Developers

Developer and agent interfaces

Four interfaces over the same public catalogue: what Speq is, the three kinds of request, the fields and the prices. All read-only, no key and no sign-up.

Public API

Read-only, no key and no sign-up. Described by a full OpenAPI 3.1 document.

/api/v1Resource index
/api/v1/summaryWhat Speq is and how a request works
/api/v1/request-kindsThe three kinds of request and what decides each
/api/v1/fieldsFields, with an example request in each
/api/v1/plansWhat each side pays
/openapi.jsonOpenAPI 3.1 description

Every resource takes ?locale=he|en. Errors are JSON in one shape, at every status.

MCP server

JSON-RPC 2.0 over a single POST, four read-only tools.

/api/mcpThe endpoint. GET describes it, POST speaks the protocol
/.well-known/mcp.jsonDiscovery

Tools: speq_summary, speq_request_kinds, speq_fields, speq_plans.

Markdown

Every marketing page also exists as markdown.

/en/suppliers.mdAdd .md to any URL
/llms.txtSite summary
/agents.mdWhen to use Speq, and what is not available
/pricing.mdPricing

Or ask for Accept: text/markdown at the same URL.

What is not here

Requests, bids, organizations and the opportunity feed are not exposed to any of these interfaces. They are visible to signed-in suppliers inside the application, and a machine asking does not change who may see them.

Questions: contact@speq.pro