gankdat
영국 및 EU 입찰, 영국 계획, 영국 제재, 미국 제외, 영국 파산 및 회사 데이터를 깨끗한 JSON으로 제공 — REST + MCP + x402
호스팅형 MCP 서버
npx add-mcp 'https://gankdat.com/mcp'Claude Code, Codex, Cursor 등에 설치됩니다
문서
gankdat docs
← home · machine-readable spec: /openapi.json · MCP endpoint for agents: /mcp
quickstart (60 seconds, no js needed)
# 1. Sign in at https://gankdat.com/account (email magic link, no password)
# and create a key from your dashboard (250 req/mo free, shown once)
# 2. Query procurement notices by value and CPV code (filters combine with AND)
curl -H "Authorization: Bearer fapi_..." \
"https://gankdat.com/v1/data/uk-tenders?value_amount_min=1000000&cpv_codes=45&status=active"
# 3. Query planning applications
curl -H "Authorization: Bearer fapi_..." \
"https://gankdat.com/v1/data/uk-planning?authority=109&q=extension&per_page=5"
# 4. What changed since a date — registers diff themselves daily (charities, care
# locations, schools, NHS, sponsors, food hygiene, exclusions, trade marks, gambling licences)
curl -H "Authorization: Bearer fapi_..." \
"https://gankdat.com/v1/changes/uk-charities?since=2026-09-01&change=added"
# …with the dataset's own filters: a trade-mark watch on one Nice class and a word
curl -H "Authorization: Bearer fapi_..." \
"https://gankdat.com/v1/changes/uk-trademark-journal?classes=09&q=northwind&since=2026-09-01"
# 5. Check your usage (free)
curl -H "Authorization: Bearer fapi_..." https://gankdat.com/v1/usage
for ai agents
# MCP (Streamable HTTP) — tools: list_sources, get_usage, get_changes (register deltas), and query_<dataset> for each dataset (query_uk_tenders, query_eu_ted, query_sam_exclusions, …)
"mcpServers": { "gankdat": {
"url": "https://gankdat.com/mcp",
"headers": { "Authorization": "Bearer fapi_..." } } }
# No key yet? An agent can sign its user up without a browser (no key needed for these two):
# MCP: request_api_key {email} → show the user the code → claim_api_key {request_id, claim_secret}
# REST:
curl -X POST https://gankdat.com/v1/auth/agent-signup -H "content-type: application/json" \
-d '{"email":"you@example.com","client_name":"my-agent"}' # user gets a one-click approval email
curl -X POST https://gankdat.com/v1/auth/agent-signup/claim -H "content-type: application/json" \
-d '{"request_id":"…","claim_secret":"fsig_…"}' # "pending" until approved, then the key (once)
# x402 pay-per-request (no account): GET /x402/data/uk-tenders → HTTP 402 → pay → retry
Every response uses the same envelope: {"ok":true,"data":…,"meta":…} or {"ok":false,"error":{"code","message","docs_url"}}. Errors carry stable codes (unauthorized, quota_exceeded, rate_limited, …) and validation failures list per-field details. Full reference below ↓