# Ways in

The different routes an agent can take to Delegrity.

Every route reaches the same authority path. Intake records which one a request came through, and it can't be used to skip a check.

| Route                  | Use it when                             | Status                                                            |
| ---------------------- | --------------------------------------- | ----------------------------------------------------------------- |
| REST                   | You make HTTP calls yourself            | Registered; tested end to end                                     |
| Python SDK             | Your agent is in Python                 | Registered; tested end to end                                     |
| TypeScript SDK         | Your agent is in Node.js                | Registered; tested end to end                                     |
| MCP gateway over stdio | Your agent speaks the MCP tool protocol | MCP request form registered; tested end to end                    |
| Framework adapters     | You build on an agent framework         | Framework request form registered; two adapters tested end to end |
| A2A                    | Agent-to-agent tasks                    | A2A request form registered; off by default                       |

"Tested end to end" means one real action went from proposal to a person's approval, execution, reconciliation and a verified receipt, then was read back on the same route, in our own test suite.

**Framework adapters** use the registered framework request form. They replace a tool's body with a proposal, so the original function never runs. Which frameworks are covered is shared with design partners.

**The MCP gateway** is proposal-only. It starts one process per session, listens on no port, and never calls a target. Registered means the request schema is published; it doesn't imply a connection to any outside service.