For AI agents

How AI agents and developers can read TillRadar's data: a public, read-only REST API, an MCP server and every page as Markdown.

Last updated 20 October 2026

TillRadar publishes its data on UK business bank accounts for AI agents and developers: public, read-only, no registration and no API keys (the one exception: a reader's own offer reminders, after sign-in). It is the same data you see on the site: welcome offers with their conditions, end dates and the date we checked them, account fees from providers' published tariffs, and our guides. Right now: 28 live offers and 18 accounts in the fee table, last checked 19 October 2026.

MCP server

Address (Streamable HTTP, JSON-RPC 2.0, no sessions): https://tillradar.co.uk/mcp. Client configuration:

{
    "mcpServers": {
        "tillradar": {
            "type": "http",
            "url": "https://tillradar.co.uk/mcp"
        }
    }
}

Tools (public and read-only, except the last three, which work on the signed-in reader's own reminders – OAuth sign-in):

  • list_offers – Welcome offers on UK business current accounts tracked by TillRadar: cash or gift-card bonuses, fee-free months and perks, live ones first by cash value. Each result has the conditions from the provider's terms, eligibility, end date, FSCS status, the date TillRadar checked it, a url on tillradar.co.uk to link and a ready "cite" line.
  • get_offer – All public details of one offer by id (from list_offers), plus the TillRadar articles that show it.
  • account_fees – Fees of UK business current accounts from each provider's published tariff: monthly fee (and after any free period), UK transfers, card use, paying in cash, cash withdrawals, card abroad, protection (FSCS bank or e-money), who can open it. Sorted by the ongoing monthly fee.
  • cost_ranking – TillRadar's ranking of UK business accounts by yearly cost for typical usage profiles (e.g. a new sole trader, a cash-heavy shop): first-year and ongoing cost, score and caveats. Returns available=false while the ranking is being prepared; use account_fees then.
  • search_guides – TillRadar articles for UK small businesses (business accounts, Making Tax Digital, sole trader vs limited company, selling online) matching a query: title, url, kind, dates, excerpt and the "short answer" box.
  • site_status – How many live and ended offers, fee rows and guides TillRadar has, and when the data was last checked.
  • list_my_reminders – Needs OAuth sign-in (scope reminders). The signed-in reader's "Remind me before it ends" reminders: offer, its end date, the days before the end when an email goes out, the next reminder dates and the status (on, waiting_for_email_confirmation, finished, stopped_offer_changed).
  • add_reminder – Needs OAuth sign-in (scope reminders). Sets an email reminder before a live offer's end date, like the "Remind me before it ends" button on the offer card. Only offers with an end date (ends in list_offers) qualify. The reader gets an email saying the reminder was set, with a cancel link. Setting it again for the same offer updates the days.
  • remove_reminder – Needs OAuth sign-in (scope reminders). Cancels one reminder, by id (from list_my_reminders) or by offer_id.

Your own offer reminders through MCP (OAuth 2.1)

With your permission, an agent can see, set and cancel your "Remind me before it ends" emails – the same as the button on each offer card. You sign in with a link from your email, no password, and the consent screen shows who is asking and for what. You can remove the access at any time on Your connected apps.

  • MCP clients (Claude, MCP Inspector and others) do this themselves: after the 401 they find the authorization server https://tillradar.co.uk (RFC 8414 metadata), register (RFC 7591) and open the sign-in window. PKCE S256, 1-hour tokens, rotating refresh tokens.
  • Agents without a browser redirect register with your email address (auth.md, service_auth): you open the link they show you, sign in by email and type the code they gave you.
  • Scope: reminders. The tools never see anything else and never return your email address.

REST API

Base: https://tillradar.co.uk/wp-json/tr/v1. OpenAPI 3.1: /openapi.json. API catalog (RFC 9727): /.well-known/api-catalog.

EndpointReturns
GET /offerswelcome offers, live by default and highest cash value first; filters segment (sole_trader, ltd), status (live, ended), provider, min_bonus, limit
GET /offers/{id}one offer, with the TillRadar articles that show it
GET /accountsaccount fees; filters segment, provider, fscs
GET /rankingaccounts ranked by yearly cost per usage profile (profile, limit); available: false while it is being prepared
GET /guidespublished guides and hubs; q, kind, limit
GET /statuscounts and data freshness

Example: curl "https://tillradar.co.uk/wp-json/tr/v1/offers?segment=sole_trader&limit=3"

Pages as Markdown

Every page (the homepage, guides, hubs, this page) returns clean Markdown when the client sends Accept: text/markdown. Browsers get HTML as before. Site map for language models: /llms.txt; full data: /llms-full.txt.

Discovery

Rules of use

  • Limit: 60 requests per minute per IP address (REST and MCP together). Over the limit: HTTP 429 with Retry-After.
  • Citing: link to the TillRadar page in the url field and give the checked date and any end date. Each result has a ready cite line.
  • No promises: the provider decides who gets an offer, and its terms prevail. TillRadar is not authorised by the FCA; this is information, not financial advice.
  • Privacy: the API and the public MCP tools take no personal data, store nothing and need no cookies or sign-in. The reminder tools work only on the signed-in reader's own reminders (privacy policy).
  • Content: TillRadar's content is protected by copyright; quoting with attribution and a link is welcome (terms of use). Preferences for AI use are declared in robots.txt.
  • Status: /wp-json/tr/v1/status. Questions and bug reports: contact.