Product
MCP ManagementHosted servers, scoped access, call logsAPI CatalogDiscover, organize, and score your APIsAPI TestingInspect quality and try your MCP toolsAPI ContractsChoose what each audience can access
How it worksPricingBlogDocsAbout SutraStart free
Sutra / API CONTRACTS

API CONTRACTS

One API.
Just the right access.

Your team, partners, and AI agents need different views of the same API. Make those boundaries explicit with contracts.

contracts / payment-accessINTERACTIVE EXAMPLE
One API. Different audiences.v1.0
GET/payments/{id}allowed
RESPONSE FIELDCONTRACT RULE
id✓ included
amount✓ included
customer_email••• masked
internal_note— removed

Partner access keeps payment details and hides internal context.

Switch audiences to see a different view of the same response.

01 / DEFINE

The interface is a promise.

A contract brings an audience, a set of endpoints, and field rules together. Review that promise before it reaches a consumer.

01

Choose the audience.

Start with an internal, partner, public, or agent audience. Select the operations that belong in that contract.

02

Decide field by field.

Keep useful response fields, mask sensitive values, or remove internal context from a published interface.

03

Review before release.

Use approval and publishing controls to turn a proposed contract into a versioned artifact your consumers can use.

02 / EVOLVE

See the change before
your consumers feel it.

Compare scans and inspect which contracts are affected when the underlying API changes.

PREVIOUS SCHEMA
{
  "amount": "integer",
  "currency": "string"
}
PROPOSED SCHEMA
{
  "amount": "string",
  "currency": "string"
}
!
A type change deserves a review.

Check affected consumers before publishing the next contract version. Illustrative diff.

A FEW DETAILS

Good questions.

Talk to us →
Is a contract the same as an OpenAPI file?

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.

Does a contract replace upstream authorization?

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.

BUILD WITH SUTRA

Make the boundary explicit.

Start free