Developer platform · controlled beta

Licensed award data and qualitative supplier-category signals.

REST, MCP and x402 capabilities remain a controlled beta. They are not included in a public paid plan until metering, settlement and support controls pass production review.

REST API

GET /api/v1/projects?sector=heritage&evidence=source-mentioned&limit=20&offset=0
GET /api/v1/projects/{slug}
POST /api/v1/match

Responses include the award source, licence, attribution, publisher-data coverage, catalogue timestamp, evidence excerpt and qualitative evidence level. They deliberately exclude supplier-spend estimates, invented buying windows and probability percentages. See the OpenAPI specification.

Model Context Protocol

The MCP endpoint exposes read-only project search and supplier-match tools with the same provenance and qualitative evidence contract as REST.

POST /api/mcp
Authorization: Bearer fsp_live_…

x402 beta

Pay-per-request settlement remains disabled until the owner-controlled receiving wallet, facilitator credentials, metering and live payment tests are complete. No public x402 availability is promised.

Evidence contract

Confirmed procurement is reserved for a direct procurement notice or equivalent observable source.
Source-mentioned activity means the award text explicitly describes a relevant delivery activity.
Possible supplier category is a category-level inference and must be verified before outreach.

Guardrails

Rate and monthly usage limits apply during beta.
Bulk extraction is not included.
Source licence and attribution travel with every result.
Personal contact details are not sold through the API.
Signals are not confirmed tenders, budgets, buying dates or purchase probabilities.