Tenders Brief
by ukintel in Documents & files
One tender as a full agent-ready dossier: parsed requirements summary, buyer, value, complete timeline with working-days-remaining, lots, document links, submission route and the official notice URL. CPV codes are null when the source release carries none - we report the register, we never guess.
https://api.ukintel.uk/v1/tenders/:ocid/brief- Price
- $0.1
- per call in USDC
- Uptime
- 0.0%
- last 30 days
- Response time
- -
- no timed checks yet
- Last check
- Failed
- 2 h ago, next any minute now
Reliability
Latest check failed 2 h ago: Expected HTTP 402, got 403
Status and outage history · Atom feed · Watch with other listings
How to call it
GET https://api.ukintel.uk/v1/tenders/:ocid/brief
Each call costs $0.1 in USDC on Base, paid with the request over x402.
Run a free test callOne unpaid request, the way an agent sends it. You see the payment challenge it gets back. Nothing is charged.
Example request
From the listing.
GET https://api.ukintel.uk/v1/tenders/:ocid/briefExample response
The provider's example. We can't check it without paying.
Example response, 26 lines
{
"confidence": "high",
"notice": "Information, not advice.",
"query": {
"ocid": "ocds-h6vhtk-06df8b"
},
"result": {
"buyer": "Hull City Council",
"cpv": [
{
"code": "90733000",
"desc": "Services related to water pollution"
}
],
"deadline": "2026-09-02T11:00:00+00:00",
"source": {
"name": "Find a Tender",
"notice_url": "https://www.find-tender.service.gov.uk/Notice/075483-2026"
},
"title": "Provision of Water Testing Services",
"value": {
"amount": 180000,
"currency": "GBP"
}
}
}Call it from code
The curl command shows the payment challenge. The JavaScript and Python versions pay and call, and never pay more than $0.1.
curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i 'https://api.ukintel.uk/v1/tenders/:ocid/brief'
# x402 v2 sends the challenge base64-encoded in the PAYMENT-REQUIRED header (v1 sends it in the body).
# To read the header:
curl -sS -g -o /dev/null -D - 'https://api.ukintel.uk/v1/tenders/:ocid/brief' \
| grep -i '^payment-required:' | cut -d' ' -f2 | tr -d '\r' | base64 --decodeJavaScript: pay and call
// npm i @x402/fetch @x402/evm viem
import { wrapFetchWithPayment, x402Client } from "@x402/fetch";
import { registerExactEvmScheme } from "@x402/evm/exact/client";
import { privateKeyToAccount } from "viem/accounts";
// Pays at most $0.1 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.1" });
registerExactEvmScheme(client, { signer: privateKeyToAccount(process.env.EVM_PRIVATE_KEY) });
const pay = wrapFetchWithPayment(fetch, client);
// Not sure it's safe to pay? ToolVet checks it first for $0.005. Pay for that from a separate
// client: this one is capped at $0.1 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fapi.ukintel.uk%2Fv1%2Ftenders%2F%3Aocid%2Fbrief
const res = await pay("https://api.ukintel.uk/v1/tenders/:ocid/brief");
console.log(res.status, await res.text());Python: pay and call
# pip install "x402[requests,evm]"
import os
from eth_account import Account
from x402 import x402ClientSync
from x402.http.clients import x402_requests
from x402.mechanisms.evm import EthAccountSigner
from x402.mechanisms.evm.exact.register import register_exact_evm_client
# Pays at most $0.1 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.1"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))
with x402_requests(client) as session:
res = session.get("https://api.ukintel.uk/v1/tenders/:ocid/brief")
print(res.status_code, res.text)Security scan
No findings
We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.
Recent checks
| When | Result | HTTP | Time | Price |
|---|---|---|---|---|
| 2 h ago | Expected HTTP 402, got 403 | 403 | 220 ms | - |
| 7 h ago | Expected HTTP 402, got 403 | 403 | 214 ms | - |
| 12 h ago | Expected HTTP 402, got 403 | 403 | 234 ms | - |
| 17 h ago | Expected HTTP 402, got 403 | 403 | 245 ms | - |
| 21 h ago | Expected HTTP 402, got 403 | 403 | 503 ms | - |
Show 10 older checks
| 26 h ago | Expected HTTP 402, got 403 | 403 | 316 ms | - |
| 31 h ago | Expected HTTP 402, got 403 | 403 | 270 ms | - |
| 36 h ago | Expected HTTP 402, got 403 | 403 | 240 ms | - |
| 40 h ago | Expected HTTP 402, got 403 | 403 | 288 ms | - |
| 45 h ago | Expected HTTP 402, got 403 | 403 | 259 ms | - |
| 2 days ago | Expected HTTP 402, got 403 | 403 | 226 ms | - |
| 2 days ago | Expected HTTP 402, got 403 | 403 | 146 ms | - |
| 2 days ago | Expected HTTP 402, got 403 | 403 | 181 ms | - |
| 3 days ago | Expected HTTP 402, got 403 | 403 | 237 ms | - |
| 3 days ago | Expected HTTP 402, got 403 | 403 | 291 ms | - |