Choose the audience.
Start with an internal, partner, public, or agent audience. Select the operations that belong in that contract.
API CONTRACTS
Your team, partners, and AI agents need different views of the same API. Make those boundaries explicit with contracts.
/payments/{id}allowedPartner access keeps payment details and hides internal context.
01 / DEFINE
A contract brings an audience, a set of endpoints, and field rules together. Review that promise before it reaches a consumer.
Start with an internal, partner, public, or agent audience. Select the operations that belong in that contract.
Keep useful response fields, mask sensitive values, or remove internal context from a published interface.
Use approval and publishing controls to turn a proposed contract into a versioned artifact your consumers can use.
02 / EVOLVE
Compare scans and inspect which contracts are affected when the underlying API changes.
{
"amount": "integer",
"currency": "string"
}{
"amount": "string",
"currency": "string"
}Check affected consumers before publishing the next contract version. Illustrative diff.
The contract selects an audience-specific view of your catalog. An OpenAPI document is one artifact you can generate from that view; a Postman collection and MCP tools can use it too.
No. Your API must continue enforcing its own authorization. Sutra adds an explicit published interface and gateway controls; it does not make upstream access checks unnecessary.