Sign in
Google, GitHub or email. Ten seconds, no credit card, nothing to configure.
For founders shipping an API
Make your API theeasiest one they ever integrated.
DocentAPI learns your API by actually running it — then answers every question your customers’ engineers ask, hands their agents a hosted MCP server, and keeps both in sync every time you ship.
Sign in, paste your spec and a dev key. About a minute.
Read-safe calls only — the key is never stored.
Two steps to live~1 min
Sign in
Google, GitHub, or email. No card.
Paste your spec and a dev key
OpenAPI, a Postman collection, or one cURL command.
Then, without you
- Every read-safe endpoint run and recorded
- Your MCP server, live at a URL you own
- Docs that answer questions, not just describe fields
Live on
[LOGO][LOGO][LOGO][LOGO][LOGO]
What you get
Three things, from one paste.
01
It knows your API as well as your own team does.
Not because it read the spec — because it ran it. Every read-safe call executed, every field traced to where its value actually comes from, every answer backed by a recorded response.
- Anyone can ask it anything — in your docs, in Slack, in their editor
- It knows which call produces the id the next one needs
- When it does not know, it says so — it never invents a field
Integrations that took[3 WEEKS]now take[2 DAYS]
Your customer’s engineer, 11:04docs · slack · editor
you ›what do I put in source on POST /charges?
source is caller_supplied — the only field on this call you actually choose. It takes either:
- 01a token id from POST /tokens → .id
- 02a saved card id from GET /customers/{id}/sources
The other nine fields are server-generated or fixed. You do not need to send them.
Verified against a live call · 2h ago
Worked example — not an answer about any real API.
02
A hosted MCP server, from the same paste.
One URL your customers drop into Claude, Cursor or Copilot — and their agents are calling your API. You are the vendor with an MCP server, and you built nothing.
- Zero infrastructure on your side — we host it and run it
- Tools verified by execution, not transpiled from the spec and hoped over
- Every tool marked read or write, so nothing destructive fires blind
www.docentapi.xyz/mcp/acmeready
list_customersread
create_chargewrite
refund_chargewrite
get_invoiceread
+ 34 more tools · auth handled · rate-limited0 lines of your code
Illustrative tool list — your API decides the real one.
03
You ship a change. It updates itself.
We watch your spec and your live endpoints. The moment something moves we classify it, re-run the checks, and update the docs and the MCP tools together. Nothing drifts. Nobody gets paged.
- Breaking changes flagged before your customers find them
- Docs and MCP tools update in the same pass — never one without the other
- A dated ledger of every change, so you can prove what moved and when
Change ledger · acmewatching, always
today 09:41
POST /charges · new field statement_descriptor_suffix
02 sep
GET /invoices · status gained "uncollectible"
28 aug
DELETE /cards · returns 204, spec still said 200
Worked example — the shape of a real ledger, not one API’s.
Getting started
Two steps. No integration project.
Nothing to install, no SDK to adopt, and no change to your API. You give us a spec and a dev key; we do the rest.
Paste spec + dev key
An OpenAPI URL, a Postman collection, or a single cURL command. The key runs read-safe calls and is never stored.
That is the whole setup
Minutes later your answers, your docs and your MCP server are live — and stay that way on their own.
Your API is good. Make it obvious in a day.
Paste a spec and a dev key. See what your customers would see — before you decide anything.
Connect your APIFree while your API is public · keys never stored · cancel by deleting the project