--- title: "Agent-Readable docs: Why mcp.md matters for contact APIs – Invenitor" description: "Why MCP.md matters for contact APIs: agent-readable tools, same credits as REST. Start at /mcp.md – not a scraper wiki." url: https://invenitor.com/blog/agent-readable-docs-why-mcp-md-matters-for-contact-apis agents: https://invenitor.com/llms.txt mcp: https://api.invenitor.com/mcp --- [Blog](https://invenitor.com/blog) Oct 13, 2026 · 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. On this page 1. [What MCP.md is for](#what-mcp-md-is-for) 2. [Why marketing blogs are not enough](#why-marketing-blogs-are-not-enough) 3. [REST twin remains mandatory](#rest-twin-remains-mandatory) 4. [Prompt hygiene that MCP.md enables](#prompt-hygiene-that-mcp-md-enables) 5. [Commercial path for agent owners](#commercial-path-for-agent-owners) 6. [What should you do next?](#what-should-you-do-next) 7. [Procurement language for agent-capable APIs](#procurement-language-for-agent-capable-apis) 8. [What good agent-readable docs refuse to hide](#what-good-agent-readable-docs-refuse-to-hide) 9. [Onboarding an agent in under an hour](#onboarding-an-agent-in-under-an-hour) 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](https://invenitor.com/blog/claude-cursor-agents-calling-a-contact-lookup-mcp-endpoint). ## What MCP.md is for is the machine-facing twin of . 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](https://invenitor.com/blog/linkedin-github-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 and 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 – . PAYG: [Pay-As-You-Go Contact APIs](https://invenitor.com/blog/pay-as-you-go-contact-apis-for-teams-that-hate). India checkout: [INR Credit Packs](https://invenitor.com/blog/inr-credit-packs-for-contact-lookup-how-razorpay-pricing-feels), Free-plan contrast: [The Hidden Cost of "Free Plan" Enrichment Tools](https://invenitor.com/blog/the-hidden-cost-of-free-plan-enrichment-tools-for-small). ## What should you do next? Open . Wire a test agent with a safe key. Run real shortlist URLs. Keep REST in . Buy packs on when ready. Category: [What a Contact Lookup API Actually Does](https://invenitor.com/blog/what-is-a-contact-lookup-api). Layer pick: [Contact Lookup API vs CRM vs Sequencer](https://invenitor.com/blog/contact-lookup-api-vs-crm-vs-sequencer-pick-the-right). ## Procurement language for agent-capable APIs Trust checklist: [Trust Checklist Before You Buy Any Contact API](https://invenitor.com/blog/trust-checklist-before-you-buy-any-contact-api). Definition cousins: [What Is a LinkedIn Profile URL Lookup?](https://invenitor.com/blog/what-is-a-linkedin-profile-url-lookup), [GitHub Profile URL Contact Lookup](https://invenitor.com/blog/github-profile-url-contact-lookup-when-developer-profiles-are-the). ## 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 . Primer: [What Are API Credits in Enrichment Products?](https://invenitor.com/blog/what-are-api-credits-in-enrichment-products). Trust: [Trust Checklist Before You Buy Any Contact API](https://invenitor.com/blog/trust-checklist-before-you-buy-any-contact-api). Hub: [LinkedIn or GitHub Profile URL → Contact Lookup API](https://invenitor.com/blog/linkedin-github-contact-lookup-api). Layer: [Contact Lookup API vs CRM vs Sequencer](https://invenitor.com/blog/contact-lookup-api-vs-crm-vs-sequencer-pick-the-right). Commercial: , [25 to 1,000 Credits](https://invenitor.com/blog/25-to-1-000-credits-choosing-an-inr-pack-size). Definition: [What Is a LinkedIn Profile URL Lookup?](https://invenitor.com/blog/what-is-a-linkedin-profile-url-lookup). twin stays mandatory. ## Onboarding an agent in under an hour Read . Configure Claude or Cursor per [Claude / Cursor Agents](https://invenitor.com/blog/claude-cursor-agents-calling-a-contact-lookup-mcp-endpoint). 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. ## Find the person you need Describe who you need in one sentence. Your first search is free, and you pay only for contacts we find [Find people free](https://invenitor.com/login?from=https%3A%2F%2Fpeople.invenitor.com%2Fsearch&x=w7&q=c5&z=g1)[See pricing](https://invenitor.com/pricing?x=w7&q=c5&z=g2) ## Keep reading - [Oct 5, 2026 · MCPClaude / Cursor agents: Calling a contact lookup MCP endpointClaude and Cursor agents calling a contact lookup MCP endpoint: tool calls instead of scrapers – same credits as REST.](https://invenitor.com/blog/claude-cursor-agents-calling-a-contact-lookup-mcp-endpoint) - [Nov 4, 2026 · PricingEvaluating contact APIs without "best of" roundupsEvaluating contact APIs without "best of" roundups – a buyer rubric for honesty, billing, docs, and workflow fit. Rubric beats rankings.](https://invenitor.com/blog/evaluating-contact-apis-without-best-of-roundups) - [Nov 4, 2026 · ProductNever make one up: Editorial standards for enrichment content teamsNever make one up: editorial standards for enrichment content teams – ban invented demo contacts, hit-rate claims, and marketing that contradicts the API.](https://invenitor.com/blog/never-make-one-up-editorial-standards-for-enrichment-content-teams)