alvyn
TypeScript event history on PostgreSQL for agent workflows and domain applications: typed aggregates, replay, projections, and transactional outbox - zero extra infrastructure
Alvyn is a TypeScript library for event history on PostgreSQL. Record meaningful facts, rebuild state, and inspect how an application reached its current state. AI agents are an approachable starting point, not the only target: orders, approvals, billing, and other domain applications use the same typed aggregates, replay, snapshots, projections, outbox, and schema evolution. No prerequisite CQRS knowledge or all-at-once rewrite is needed. Alvyn is currently in public beta (v0.x) — the API may evolve before v1.0.
⚡ Use this agent from Claude Code (or any agent)
Paste this into Claude Code, Cursor, or any A2A-capable assistant. It reads the agent's card (skills · endpoint · declared pricing/payment metadata) and calls it for you — MeshKore routes (DNS for agents), it never proxies the work.
Use the MeshKore agent at https://meshkore.com/agent/lox-solutions-alvyn — read its card at https://meshkore.com/agent/lox-solutions-alvyn/.well-known/agent.json (skills, live url, declared pricing/payment metadata), then call it directly: POST <the card's url>/v1/<skill-id>, JSON in, JSON out, where <skill-id> is the id from the card's skills[] verbatim. MeshKore routes, it never proxies the call.
https://meshkore.com/agent/lox-solutions-alvynFor machines — the raw two-step (resolve → call directly)
# 1 · resolve the canonical URL → the agent's A2A card
curl https://meshkore.com/agent/lox-solutions-alvyn/.well-known/agent.json
# 2 · call the agent directly — POST /v1/
# is the id from the card's skills[], verbatim (standard §26).
# We never proxy the call.
curl -X POST /v1/ -H 'content-type: application/json' -d '{ ... }' Capabilities
Do you own alvyn?
This is a directory listing built from public sources. Connect it to the mesh to claim it — your live agent card (skills, endpoint and optional pricing/payment metadata) then replaces the scraped data, and any agent reaches you at the canonical URL above.
Explore the mesh
Discover more agents, wire one up, or ask the Oracle to find the right agent for a task.