Open source

Open all the way down.

Schemas, skills, reference servers, and report templates are all open. No component requires a TinyRFP-operated service to function — the project is complete on its own.

The repositories

Four repos, one specification

The specification is a set of versioned documents and schemas, maintained like any open-source project.

tinyrfp-specComing soon

JSON Schemas for the brief, vendor profile, Q&A exchange, evidence record, and shortlist report — plus the discovery convention and a conformance test suite.

tinyrfp-buyerComing soon

The authoring skill, the research agent and its harness, industry modules, the rubric library, and the report templates and renderer.

tinyrfp-vendorComing soon

The reference MCP server, the onboarding kit, a generator for the discovery files, and deployment recipes for Docker, Vercel/Cloudflare, and CMS plugins.

tinyrfp-registryComing soon

A later, optional federated index of provider endpoints — domain-verified and conformance-crawled. Never a mandatory gatekeeper.

How it's governed

Deliberately ungoverned

A proposal, not a standard

Following the llms.txt model: publish a concrete, well-specified idea with working reference code, and let adoption be the verdict. No foundation, no steering group, no certification authority.

No mandatory registry

Discovery works from open web search and per-domain probing. Any community index is optional and federated — never a gatekeeper.

Conformance is self-assessed

Run the public validator. A passing badge means exactly 'the validator passed on this date' — nothing more, and there's no body to appeal to.

No paid placement, ever

There is no way to buy ranking or visibility anywhere in the project. That neutrality is the project's core credibility asset.

Licensing & portability

Yours to run, anywhere

The code is licensed under MIT and the specification documents under CC‑BY 4.0. You can fork, extend, and self-host any part of it.

It's model-agnostic and host-agnostic by design. The buyer skill runs in any agent host that supports skills and MCP; the vendor server speaks standard MCP. Nothing here depends on a specific model vendor or a hosted TinyRFP service.

If it ever needs a neutral home

Should the project gain real traction, the intended path is donation to an existing neutral steward — not building governance in-house.

The repositories are coming soon.

The spec, buyer, and vendor repos will be published openly — schemas first, with working reference implementations alongside.

Coming soonSee how it works