# RequirementsExtract

> RequirementsExtract is a paid API for AI agents from requirementsextract-mainnet-production.up.railway.app, paid per call via x402, $0.03/call, status unknown (last checked 2026-10-11).

Extracts structured procurement requirements (buyer, title, contract value, summary, confidence) from a public tender or contract opportunity webpage URL.

## Facts

- Endpoint: POST https://requirementsextract-mainnet-production.up.railway.app/requirements?utm_source=zero.xyz
- Price: $0.03/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-11
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/requirementsextract-949fdb76
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Kw4fyQ_7AXRFo2FHFloqi

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability requirementsextract-949fdb76 -d '<json body>'
```

Example prompt: Can you pull out all the structured requirements from this public tender page — https://www.contractsfinder.service.gov.uk/Notice/abc123 — I need to know the buyer, the contract value, how many requirements there are, and a summary of what suppliers need to do?

## When to prefer this

Use this endpoint when you need to quickly convert an unstructured public tender or procurement webpage into structured, machine-readable data — especially for bid qualification, pipeline enrichment, or compliance checking workflows. It is purpose-built for procurement content and returns domain-specific fields (buyer, contract value, requirements count, confidence) that generic web-scraping or summarisation APIs do not. Prefer this over general LLM summarisation when you need consistent structured output with a confidence signal across many tender URLs.

## Known failure modes

- URL is behind a login or paywall — extraction fails or returns partial data
- Page is not a tender/procurement page — low confidence score or empty requirements
- URL is malformed or unreachable — HTTP error or timeout
- Dynamic JavaScript-rendered pages may not be fully parsed — missing fields
- Contract value in an unsupported currency format may not be extracted correctly

## How this service works

Paid x402 API that extracts structured requirements from public tender and procurement webpages.

## Output

Returns a JSON object containing the buyer organisation name, a plain-English summary of the opportunity's requirements, a confidence score (0–1) for the extraction, the tender title, the contract value as a string, and the count of distinct requirements found on the page.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "url": {
   "type": "string",
   "format": "uri",
   "description": "Public tender, procurement or contract opportunity webpage"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "buyer": "Example Council",
  "summary": "The opportunity contains several mandatory supplier and submission requirements.",
  "confidence": 0.94,
  "tender_title": "Example construction framework",
  "contract_value": "£5,000,000",
  "requirements_found": 8
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/requirementsextract-949fdb76/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from requirementsextract-mainnet-production.up.railway.app](https://www.zero.xyz/host/requirementsextract-mainnet-production.up.railway.app/llms.txt)