Getting started
Every address starts https://api.councilmonitor.co.uk/v1/ (the /v1 may be left off). Answers are JSON, always in one envelope: data with the records and meta with counts and notes, or error when something is wrong. No sign-up, no key: try it.
curl "https://api.councilmonitor.co.uk/v1/meetings?council=adur-and-worthing&upcoming=true"
The whole reference in one file for your assistant or to read offline: manual.md. For tools: OpenAPI and a Postman collection.
/v1/councilsEvery council covered, with its slugNo key neededGET/v1/councils/{slug}One council: its name, its official site and how much of it is in the archiveNo key neededGET/v1/meetingsMeetings, newest first, or coming up first with upcoming=trueNo key neededGET/v1/meetings/{id}One meeting with its agenda: every item, what was decided and its papersNo key neededGET/v1/items/{id}One agenda item: the decision in the council's words, the minutes and its papersNo key neededGET/v1/decisionsDecisions councils have recorded, newest first, or best match first with qNo key neededGET/v1/papers/searchSearch the words inside every paper: officer reports, minutes, agendas and appendicesNo key neededGET/v1/papers/{id}One paper: where it belongs, its pages and its opening (the full text with a key)No key neededGET/v1/papers/{id}/textA paper's full text, in parts of 30,000 charactersPro Plus keyGET/v1/usageWhat this key or address has used, its limits and when they reset (not counted)No key needed Keys
Without a key the API gives every meeting, item and decision, paper search with a quoted line, and the opening of each paper, 60 requests an hour from one address. A free key, made on any account, covers those same endpoints at 1,000 requests a day. A Pro Plus key adds the full text of every paper and 250,000 a month. Make keys on your account (each can be revoked); the same keys work with the MCP server. Pro Plus also has webhooks: your own endpoints told the moment a paper, decision or agenda lands, in the same record shapes.
How to send your key, and rotating it, is in the Authentication guide.
Authentication
Send your key in a request header, either form:
Authorization: Bearer cmk_... X-API-Key: cmk_...
A key in the address (?key=) is refused with a 400, so it never lands in a log or a browser history. Make and revoke keys on your account; the same keys work with the MCP server.
To rotate a key, make a new one, move your calls across, then revoke the old. A free key gives the open endpoints at 1,000 requests a day; a Pro Plus key adds the full text of papers and 250,000 a month.
Limits
| Requests | Full text of papers | |
|---|---|---|
| No key | 60 an hour from one address | The opening 1,500 characters |
| Free key | 1,000 a day | The opening 1,500 characters |
| Pro Plus key | 250,000 a calendar month, with the MCP server | All of it, in parts of 30,000 characters |
| Data licence | Agreed with us | All of it, plus whole-archive delivery |
Every answer carries X-RateLimit-Limit, X-RateLimit-Remaining and X-RateLimit-Reset (Unix seconds); a key's answers add X-Quota-Remaining. /v1/usage shows the same without using a request.
Errors
An error is {"error": {"code", "message", "docs"}}, with plan when a plan would allow it. The message is for people; the code is for code, and never changes.
| Code | Status | When |
|---|---|---|
bad_request | 400 | A value is not in its shape: a date, a number, one of a list, or a key in the address |
unauthorized | 401 | The key is not one of ours, or has been revoked |
upgrade_required | 403 | The endpoint needs a Pro Plus key |
not_found | 404 | No such council, meeting, item, paper or endpoint |
unknown_parameter | 422 | A parameter the endpoint does not take: the message lists the ones it does |
rate_limited | 429 | The hourly limit without a key: Retry-After says when it frees up |
quota_exceeded | 429 | A key's month is used up: it resets on the 1st |
server_error | 500 | Our fault; it is logged |
An empty result is not an error: it is a 200 with meta.count at 0.
Pages of results
Lists take page (from 1) and per_page (up to 100, 25 by default). The first answer's meta has count, page, per_page, total, total_pages, next_page and prev_page, plus next_cursor. To walk a long list, send cursor instead of page: those answers carry only count and next_cursor, which is faster. total is null where counting everything would be slow.
Ids and links
Councils are named by their slug (adur-and-worthing). Meetings, items and papers have ids of their own: mt_, it_ and pp_ followed by eight letters and digits. They stay the same for good. Every record carries link, its page on CouncilMonitor, and official_url, its address on the council's own site.
Dates are the council's own day, YYYY-MM-DD; times are as the council gives them. A meeting's state is upcoming, today or held. Version 1 only ever gains fields: none is renamed, retyped or removed.
Use with Claude and agents
The CouncilMonitor agent skill is one markdown file that tells Claude, Cursor, Codex and other agents what CouncilMonitor answers, which endpoint or MCP tool to call for each question, the limits and the error codes. Agents that look for skills find it by themselves at /.well-known/agent-skills/index.json.
To install it, save it as ~/.claude/skills/councilmonitor/SKILL.md, or upload it as a skill in Claude's settings. The MCP server works alongside it with the same keys.