Use this API in your AI agent

Free trial: POST /v1/trial, save the returned API key (shown once). Paid: POST /v1/checkout, complete card payment via Stripe and return to /success for instant activation.

Send Authorization: Bearer YOUR_API_KEY with each protected request. Trial: 3 days, 10 calls/day, 1 custom monitored GOV.UK URL. Paid: £9 once for 30 days, 100 calls/day, 3 custom monitored URLs.

Monitor your own GOV.UK page

curl -X POST 'https://uk-source-intelligence.pages.dev/v1/watches' -H 'Authorization: Bearer YOUR_API_KEY' -H 'Content-Type: application/json' -d '{"url":"https://www.gov.uk/vat-rates"}'

Use another supported https://www.gov.uk/... URL to create a custom watch (the example is already part of the fixed watchlist). List watches with GET /v1/watches; remove one with DELETE /v1/watches?url=ENCODED_URL. Check its records with GET /v1/history?url=ENCODED_URL or GET /v1/changes?url=ENCODED_URL.

Inspect current guidance

curl -X POST 'https://uk-source-intelligence.pages.dev/v1/inspect' -H 'Authorization: Bearer YOUR_API_KEY' -H 'Content-Type: application/json' -d '{"url":"https://www.gov.uk/vat-rates"}'

Limitations: GOV.UK Content API rendered fields only. No PDFs, linked attachments, legal interpretation or general web monitoring. Saved change histories begin when first polled. Customer checks use a fair scheduled queue; 15 minutes is a poll cycle, not a guaranteed per-page interval. Only paid customers authorised for card purchases should start paid checkout; an agent must not purchase without its owner's permission.

OpenAPI specification · Agent discovery summary · Back