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
MADE IN INDIAFor India’s API stack

API management,rebuilt for India’sagentic era.

Discover the APIs in your code. Govern what each audience can access. Connect them to developers and AI agents. Catalog, contracts, and MCP servers. One pipeline.

A personal walkthrough · Bring your API questions

sutra / kirana-paymentsExample workflow
❯ python3 -m sutra.cli scan ./payments-api
Reading routes, handlers, and schemas
✓ 214 endpoints discovered
✓ OpenAPI 3.1 generated from source
✓ 5 categories scored
! 31 descriptions could be clearer
✓ Catalog ready. Your contract comes next.
214ENDPOINTS
71%AI READINESS
23MCP TOOLS

Works with the tools your APIs already live in

GitHub Postman OpenAPI 3.1 Swagger Claude Cursor VS Code Gemini CLI Codex CLI
01 · DISCOVERAutomatic API discovery

Turn your repo into a complete API catalog,
even without specs.

Connect your repository. Sutra finds the routes and schemas, generates an OpenAPI spec, and scores every endpoint. No manual inventory required.

Your catalog is ready. Choose a step to look closer.

04 / 045.1s

From source to catalog to governed MCP tools. An illustrative workflow.

214ENDPOINTS DISCOVERED
89%AUTH COVERAGE
23TOOLS EXPOSED
73%AGENT-READY
02 · UNDERSTANDAPI scoring & insights

Know how agent-ready
your APIs really are.

Every endpoint scored on design, security, and AI readiness. See exactly what needs attention. Then improve the documentation with AI.

Your API results by category

Example workspace · 12 API collections

Scored
A complete view of API quality5 categories

Hover to explore. Click a category to keep its insights in view.

BEFOREC · 71%

AI readiness

  • !31 endpoints missing descriptions
  • !18 summaries missing context
  • !Unclear response behaviour

AI readiness · payments-api

AFTER71%

Ready to improve

  • ·31 descriptions generated
  • ·18 summaries clarified
  • ·Response context added

Click “Improve with AI” to run the example

An illustrative walkthrough. Your scores and suggested improvements depend on your code.

03 · GOVERNAudience-aware contracts

API contracts decide
what ships.

Choose the audience, endpoints, and fields they can see. Publish that contract, then catch breaking changes before you publish the next version.

BUILD A CONTRACTInteractive example · choose a step below

Step 1 · Who is this contract for?

Step 2 · Which endpoints does the partner get?

GET/payouts/{payoutId}included
POST/payoutsincluded
GET/upi/collect/{txnId}/statusincluded
POST/upi/mandateincluded
DELETE/builds/{id}excluded
GET/internal/ledger/rawexcluded

Step 3 · Which fields leave your perimeter?

payout.idexposed
payout.amount · payout.currencyexposed
payout.utrexposed
payee.vpamasked · DPDP
payee.panredacted · DPDP
internal.riskScoreblocked

Step 4 · Where does this contract ship?

Developer portal · docs.kirana.in/partnerspublish
OpenAPI 3.1 bundlepublish
Hosted MCP server · 2 toolspublish
Postman collectionpublish
Changelog & partner emailon approval

Step 5 · Live and watched

v1.4payouts-partnerlive · 1 partner
CIDiffed on every push to mainarmed
CIBreaking change blocks the mergeenforced
LOGEvery partner call attributed to a keyrecorded

Someone shipped 5 changes today. Two would have broken a partner. Sutra stopped them.

openapi.yaml · Build
Build:
properties:
id: { type: string }
status: { type: string }
- buildLog:
- type: string
- description: Full build output
+ logUrl:
+ type: string, format: uri
Impact
!Consumers reading buildLog2 services
!Partner builds affected1 partner
~MCP tools referencing field1 tool
Publish blocked by policy
openapi.yaml · security
/upi/collect/{txnId}/status:
get:
- security: [ { partnerKey: [] } ]
+ security:
+ - partnerKey: [ upi:read ]
+ - mtls: []
Impact
!Partner keys without upi:read1 partner
!Agents calling the tool today34 calls/day
✓Sandbox unaffectedno change
Publish blocked by policy

Click any change to see the exact schema diff and who it breaks.

04 · PUBLISHMCP server generation & hosting

Run your MCP servers
like real infrastructure.

Generate an MCP server from your API catalog. Hosted or self-hosted, authenticated through Sutra’s gateway, with every tool call logged.

SUTRA GATEWAY

Scoped. Authenticated. Logged.

200 OKClaude Desktopget_payment_status42ms

Claude, Cursor, or any MCP client.
Choose a client to follow its tools through the gateway.

CONNECT YOUR FIRST AGENT

One command.
Every tool in reach.

Publish your server, copy its URL from the dashboard, and add it to your favourite MCP client.

CLAUDE CODEHTTP transport
claude mcp add --transport http payments YOUR_MCP_URL

Replace YOUR_MCP_URL with your published server URL.

Hosted or self-hostedServer access controlsFull call logs
Create your first MCP server

05 · India Stack

The rails your APIs already sit on

Sutra includes beta reference transcriptions for UPI, ONDC and GSTN. Compare them with your API, and verify each against the authority's own specification before relying on it.

UPI
UPI / NPCI

Collect, mandate and payout reference schemas.

Beta transcription
ON
ONDC

Beckn search, select, init and confirm reference schemas.

Beta transcription
AA
Account Aggregator

Consent and FI data fetch contracts in development.

Planned
DL
DigiLocker

Issued-document and eSign support in development.

Planned
GST
GSTN

E-invoice IRN and e-way bill reference schemas.

Beta transcription
BBP
Bharat BillPay

Biller discovery, fetch and payment confirmation.

Planned
KYC
CKYC / eKYC

Offline Aadhaar XML and CKYC search contracts.

Planned
OCN
OCEN

Loan agent and lender API contracts for embedded credit.

Coming soon

06 · Improve

Try the playground, then read the agent feedback

Test the server with a real agent in the playground. Once it is live, the agents calling it tell you which tools confused them.

MCP Playground · kirana-payments v2 · 23 tools
Test your MCP tools

Ask the agent to do something with your server. It picks the tools and shows you every call it made.

Claude Sonnet 4.6
Agent feedback · 3 open · 1 critical
ClaudeCRITICAL2h ago

The tool description does not clearly explain when it should be used versus list_transactions.

GET/customers/{customerId}
ChatGPT4h ago

The tool failed to return a response after multiple attempts — the MCP server kept timing out on the UPI callback.

POST/orders
Cursor4h ago

The tool requires too many parameters for a simple lookup. Six of nine could be optional.

GET/products/{productId}
filed by the agents calling kirana-payments v2 · scored into the catalog

07 · Observe

See what happened on every MCP call

Inspect the tool, key fingerprint, outcome, and latency. The activity below is an illustrative example.

payments MCP server · example activity
TOTAL REQUESTS
847
↑ 6.7% from yesterday
AVG RESPONSE
38ms
P95 141ms · sample
ERROR RATE
3.2%
27 failed · 847 total
TOKEN USAGE
1.05M
avg 1,240 per call
API KEY · 24HCALLSAGENTSERRORS
Example key A ****7f2a · most used: sutra_get_payouts612618
Example key B ****3e1b · most used: sutra_auth_login14926
Example key C ****a4c0 · most used: sutra_get_analytics8613

Illustrative data. Sutra records each call's tool, key fingerprint, latency and outcome.

In practice

What changes once every call is governed

Three scenarios modelled on the reference workload — what governed MCP servers, structured errors and per-audience contracts change in practice. Illustrative figures, not customer data.

489,000
Tool calls, zero surprises

Ninety days of one MCP server at four agents’ worth of traffic. Every anomaly arrives attributed to a specific agent and key, so triage starts with a name instead of a grep.

71%
Fewer retries in a week

At 1.2 million tool calls, a single vague error message can drive a third of all retry traffic. Structured errors that name the offending field cut it.

31
Zombie endpoints retired

A first quarter on contracts, on a catalogue this size. Consumer mapping is what lets you prove nothing active referenced an endpoint before you delete it.

Enterprise

Answers the security review before it asks

Review the controls Sutra provides for access, publishing, and audit history. Discuss any regulatory or assurance requirement with us before relying on a specific commitment.

Controls you can inspect

Workspace roles
owner · admin · member
Scoped API keys
per server
Field rules
mask · redact · block
Audit history
exportable
SSO and SCIM
configurable
Self-hosting
documented

Sutra does not claim SOC 2 or ISO 27001 certification. Ask us for current assurance details.

Deployment options

Hosted SaaS

Hosted dashboard and MCP gateway · no published SLA

Self-hosted

Docker Compose, Postgres and your own TLS proxy

Custom requirements

Discuss network, data and support needs before deployment

Connect an identity provider

Sutra supports SAML and OIDC sign-in with a configured provider. Review your provider setup and the separate credentials used by agent tools.

Okta Microsoft Entra ID Auth0 Zoho Directory Google Workspace Keycloak JumpCloud SAML / OIDC standards
  • ✓SAML 2.0 and OIDC single sign-on for configured workspaces
  • ✓SCIM keeps groups, roles and deprovisioning in sync
  • ✓MCP calls record the tool, key fingerprint and outcome

Pricing

Priced in rupees, not converted into them

Start with a free workspace. Team access is ₹2,400 per workspace for a one-month term, with no automatic renewal.

Solo
₹0
Free forever

1 repo · 1 MCP server · 50 endpoints · community support. No credit card or existing spec required.

Start free
Enterprise
Custom
Discuss your requirements

Discuss identity, deployment, security review and support needs with us.

Talk to us

FAQ

Questions we get asked

Sutra reads your repositories, derives an OpenAPI 3.1 spec for every endpoint it finds, scores those endpoints on design, security and AI readiness, and then lets you publish governed slices of that catalog to partners, internal teams and AI agents — including as a hosted MCP server.
No. Your production traffic keeps flowing through whatever you already run — Kong, APISIX, Apigee, an ALB. Sutra governs the contract and hosts the MCP gateway that agents call. The two sit side by side.
No, and that is the point. Most Indian teams shipping fast have route handlers and no spec. Sutra parses the handlers, the serializers and the type hints, and writes the spec for you. If you already have one, it imports and diffs against it instead.
Sutra currently includes beta, unverified transcriptions for UPI/NPCI, ONDC's Beckn schemas and GSTN. Account Aggregator, DigiLocker and other rails are planned. Review the authority's own specification before using a transcription for compliance or production integration.
The hosted service uses Railway and Supabase, as described in our privacy policy. Confirm the current storage region and any residency requirement with us before adding sensitive data. For infrastructure you control, see the self-hosted deployment guide.
Postman starts with a collection someone maintains by hand. Sutra starts with the code and keeps the contract honest against it on every commit — then treats AI agents as a first-class audience rather than an export format.
The free plan includes one repository and one MCP server. Team is ₹2,400 per workspace for a one-month term, with no automatic renewal. Contact us to discuss deployment requirements.
Sutra is built by Prakhar Singh in India. Read more on the About page or contact us directly.

Ship APIs any agent can call

Humans, tests, partners, agents. One catalog, one contract, one place.