For solution providers
Be legible to the agents that are becoming a real buying channel.
Buyers are already sending AI agents to evaluate the market. Publish a TinyRFP endpoint and those agents get accurate answers from your own materials — and you get qualified, well-matched inbound.
An endpoint improves fidelity — it never buys ranking
The payoff
Better-matched pipeline, less wasted effort
Qualified, well-matched inbound
Buyer agents arrive with a structured brief and a committed requirements hash — not a tire-kicker filling out a form.
Fewer unwinnable RFPs
An honest fit-check lets a buyer agent disqualify early when you're not a match — saving both sides time. Honest 'does not meet' answers are a feature.
Market intelligence
See which requirements buyers bring, what they ask, and where fit-checks fall down — sanitized and within the limits you set.
Who runs it
The Champion
Head of marketing, RevOps, or sales engineering
Inbound that is qualified and well-matched — and far fewer junk RFPs. Will spend a day on setup if it produces pipeline.
The Operator
The person who maintains the content
Tooling that ingests what already exists — website, decks, security questionnaire answers — instead of demanding net-new authoring.
What you publish
A reference MCP server, from content you already have
An onboarding kit crawls your site and documents, drafts your profile, indexes your corpus, and flags gaps. The endpoint is a directory of Markdown and JSON — no database required for small corpora.
get_vendor_profileYour structured profile — identity, offerings, model.search_documentsSemantic search across your case studies, docs, and compliance summaries.get_case_studiesFilterable by industry, company size, use case, and region.get_compliance_infoCertifications and licenses with verification pointers.ask_questionGrounded Q&A — answers cite your corpus or say 'not in our materials.'check_fitAn honest, structured self-assessment against a buyer's requirements.How agents find you
Layered discovery, on your own domain
Discovery is anchored to domain control — the well-known file lives on your site over HTTPS. No central registry required.
/.well-known/tinyrfp.jsonA discovery document on your own domain — categories, regions served, your MCP endpoint, and your disclosure policy.
llms.txt entryA TinyRFP section linking the well-known file, for agents that start from llms.txt.
MCP server cardYour endpoint published where the MCP server-card convention applies.
Honesty is the winning strategy
The vendor server and onboarding kit are coming soon.
You'll be able to stand up a discoverable, queryable endpoint in under a day, using content you already have.