Skip to main content
Search UK Contracts Finder releases for procurement plans, tenders or awards within a specified date window. Operation ID: procurement.ocds. Family: Government & Procurement. Read the live operation contract (JSON) for the current input and output schemas, price, limits and required scopes. Status: Available (AVAILABLE). Supported interfaces: REST, MCP. Commercial status: Available. Receive the structured result and receipt in Console after the run settles. Execution interfaces: UI, REST, MCP.

When to use it

Find UK Contracts Finder releases for a specified date window and stage.

Price and billing unit

Request a quote for one UK public contracting release search. Review its inputs, delivery plan, use terms and maximum charge before accepting. Retrying the same purchase uses the same idempotency key. Price: $0.05. Billing unit: per successful contracting release search. Charge condition: The authorized execution delivers a validated result and settles once. Failed pre-settlement executions are not charged; reservation release must be confirmed. Retrieve the same run if charge state is uncertain. Execution budget: Maximum $0.05 per accepted execution. Fund your Console wallet, review the quote and approve the charge before execution.

Inputs

Date range up to 31 days, with optional stage, keyword, buyer or supplier

Result and output schema

Up to 25 matches within the first 100 releases scanned, with parties, stage, dates, evidence and coverage limits

Examples

Illustrative request and result for this scope. The names, values and record references are examples. Actual delivery depends on the published availability and agreed scope.

Example input

Example structured output

API example and execution

Verified production contract · Base URL: https://console.altss.com/v1/console. Quote first. Obtain explicit approval of the price, plan and use terms before sending accept:true. Reuse the same purchase idempotency key on retries. Required scope: company.read. Organization authority, funding checks and spending limits apply to paid execution. Supply credentials in the documented authorization header. Replace a placeholder run ID with an actual authorized run ID.
This example requests a quote. A paid run requires the unchanged returned quote, explicit acceptance and a stable idempotency key.

MCP and A2A

Supported interfaces: REST, MCP. Current MCP tools: altss_quote, altss_run, altss_get_run. Inspect tools/list and inputSchema before use. Paid A2A execution is unavailable. The separate anonymous A2A reader serves public information. REST guide · MCP guide · A2A scope · Authentication and credentials

Sources, evidence and freshness

  • Altss intelligence and source collections
Retain source attribution, observation and event dates, evidence and explicit unknowns where supplied. A record update is not independent verification. Historical source collection dates describe when the material was observed. Coverage and freshness depend on each returned source. Preserve its observation date and use restrictions with the result.

Limits and permitted use

  • Includes: OCDS release identifiers, titles, buyers, Companies House-identified suppliers, stages, release dates, scanned count, coverage and source attribution. Excludes: contact persons, e-mail addresses and telephone numbers; tender documents and attachments; bid or eligibility advice; bulk export. Requires scope company.read. Source: public procurement records.
  • A timeout does not establish the final charge. Retrieve the existing run before retrying.
Use is limited by the accepted quote or agreed delivery scope, source restrictions and privacy controls. Storage, attribution, retention, redistribution and training permissions do not expand through normalization.

Next step

Try Console · Open Console workspace · View the capability on Altss · Wallet and billing Back to Government & Procurement · All capabilities · Price schedule