· 9 min read · MCP
Agent-Readable docs: Why mcp.md matters for contact APIs
Agent-readable docs: why MCP.md matters for contact APIs – typed tools for Claude/Cursor agents, same found-only billing as REST.
Agents cannot safely call what they cannot read. Human marketing pages are not enough. Invenitor ships that shape: A people search and lookup API, not a sales cloud.
Claude/Cursor spoke: Claude / Cursor Agents: Calling a Contact Lookup MCP Endpoint.
What MCP.md is for
/mcp.md is the machine-facing twin of /docs. It tells an agent (or an engineer configuring one):
- Which tools exist (lookup / find).
- What inputs are valid (person LinkedIn or GitHub profile URLs).
- How to authenticate without pasting secrets into chat logs.
Hub HowTo: LinkedIn or GitHub Profile URL → Contact Lookup API.
Why marketing blogs are not enough
Blogs teach humans. Agents need typed contracts. Without MCP.md, teams fall back to scraping HTML when the model is unsure.
REST twin remains mandatory
MCP is not a replacement for REST. Product backends still call HTTP. Keep /docs and /mcp.md aligned on the same find contract.
Prompt hygiene that MCP.md enables
- "Prefer person profile URLs; reject company pages."
- "Do not scrape as a fallback."
Commercial path for agent owners
Same prepaid packs as REST – /pricing. PAYG: Pay-As-You-Go Contact APIs. India checkout: INR Credit Packs, Free-plan contrast: The Hidden Cost of "Free Plan" Enrichment Tools.
What should you do next?
Open /mcp.md. Wire a test agent with a safe key. Run real shortlist URLs. Keep REST in /docs. Buy packs on /pricing when ready. Category: What a Contact Lookup API Actually Does. Layer pick: Contact Lookup API vs CRM vs Sequencer.
Procurement language for agent-capable APIs
Trust checklist: Trust Checklist Before You Buy Any Contact API. Definition cousins: What Is a LinkedIn Profile URL Lookup?, GitHub Profile URL Contact Lookup.
What good agent-readable docs refuse to hide
Coverage varies – no fake %. Credits follow found-only billing on the same pool as REST. Scraping is not a fallback. Secrets stay out of prompts. Those refusals belong in /mcp.md. Primer: What Are API Credits in Enrichment Products?. Trust: Trust Checklist Before You Buy Any Contact API. Hub: LinkedIn or GitHub Profile URL → Contact Lookup API. Layer: Contact Lookup API vs CRM vs Sequencer. Commercial: /pricing, 25 to 1,000 Credits. Definition: What Is a LinkedIn Profile URL Lookup?. /docs twin stays mandatory.
Onboarding an agent in under an hour
Read /mcp.md. Configure Claude or Cursor per Claude / Cursor Agents. Confirm ledger.
Questions
What is MCP.md?
Agent-readable documentation for MCP tools – for Invenitor start at /mcp.md alongside /docs for REST.
Why do contact APIs need agent-readable docs?
So agents call typed lookup tools instead of scraping.
Does MCP replace REST?
No. MCP and REST should share one find contract.
Where do Claude or Cursor start?
/mcp.md plus the Claude/Cursor agents post – never scrape as a fallback.
Do agent calls use separate credits?
No – same workspace credits and found-only billing as REST.
How do I buy credits for agents?
Prepaid packs on /pricing – Razorpay/UPI for India desks.
