15 minTime to key
NoNo-human path
4Human gates
7/10Onboarding score
Email verificationKYC / business checkManual reviewTalk to sales
Fastest path to a key
- Sign up on The Bridge (bridge.setu.co/v2/signup) with an official work email + password
- Email verificationConfirm email via inbox link
- Phone OTPLog in, enter business name (optional 2FA via email OTP)
- Product store > pick a product > create a child sub-org / product instance
- Test (sandbox) credentials are issued after the child org is set up. Choose OAuth keys (Org settings > API keys; can enable/disable/regenerate) or JWT keys per product config
- KYC / business checkGo-live: fill production details + KYC (PAN, GST, certificates), submit for Setu review, sign pricing agreements. Some products (e.g. AA FIU, multi-AA) also need Sahamati/regulatory onboarding and sales contact
- Working API key
Biggest gap
No product/admin MCP or API for developers to mint sandbox keys; the only product MCP is consumer-facing BillPay
Worth copying
An llms.txt that tells the agent in its header where llms-full.txt, the markdown variant and the MCP server live, plus an AI-tools page with exact commands for every client
42Readiness score / 100
L2 Agent-documentedBeats 57% of 1,846 companies
Access20/20
Context11/20
Interfaces8/32
Onboarding0/19
Trust3/9
llms.txt · root
Biggest gains
- +12 Remote MCP server for the product. Host a remote MCP server (e.g. mcp.<domain>/mcp, Streamable HTTP) for your core actions.
- +8 Machine-readable API spec. Publish an OpenAPI spec at a stable URL like /openapi.json and link it from llms.txt.
- +6 Docs available as markdown. Serve every docs page as .md, or honour Accept: text/markdown.
All 20 checks
- PASSAgents get the real page, not a bot wall10
- PASSrobots.txt lets user-triggered agents in6
- PASSContent is server-rendered4
- PASSllms.txt exists8
- FAILllms-full.txt exists3
- FAILDocs available as markdown6
- PASSSitemap2
- PASSStructured metadata1
- PASSPublic developer docs4
- FAILMachine-readable API spec8
- FAILRemote MCP server for the product12
- FAILDocs MCP or searchable docs4
- PASSSDKs and a CLI4
- FAILOAuth discovery metadata5
- FAILAgents can self-register OAuth clients6
- FAILSelf-serve API keys5
- FAILFree tier or test mode3
- FAILAgent manifests4
- FAILsecurity.txt2
- PASSPublic status page3
Your fix pack: 12 changes, up to +58 points
Each change is ready to paste, filled in for setu.co, with a command to check it worked. Or hand the whole list to your coding agent.
Add the badge to your README
[](https://agentsready.dev/c/setu.co)