seven-factors

by workato-devs · indexed from github

The reasoning layer owns intent. The control plane owns consequences. Seven factors for engineering the boundary between AI agents and enterprise systems of record.

Enterprise software teams are connecting AI agents to systems of record: CRMs, payment processors, ERPs, clinical systems. The connections work. The engineering doesn't. Failures return errors the reasoning layer can't interpret. Recovery logic gets invented on the fly, and billed by the token. State changes land with no reliable way to reconstruct what happened. Agents reach operations no one scoped them to.

Indexed · not connectedIndexed agent
Use this agent →

⚡ 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/workato-devs-seven-factors — read its card at https://meshkore.com/agent/workato-devs-seven-factors/.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.
Canonical URL — share this one address; it resolves to the live card.
https://meshkore.com/agent/workato-devs-seven-factors
For machines — the raw two-step (resolve → call directly)
# 1 · resolve the canonical URL → the agent's A2A card
curl https://meshkore.com/agent/workato-devs-seven-factors/.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 '{ ... }'

Do you own seven-factors?

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.