Civicord · UK · Browse / Clapham and Brixton Hill

Clapham and Brixton Hill · E14001175 · Greater London · England · 75,460 electorate

Clapham and Brixton Hill

Low response rate — The rounded HTTP response rate at the audit was below 40%. Technical failures do not establish permanent removal. 1 of 3 sites responding (33%) · 2 unreachable · 0 redirected

What happened here

  1. What was recorded

    The April 2025 scrape recorded 3 candidate websites for Clapham and Brixton Hill.

    • Asha Saroy — Conservative and Unionist Party — https://www.ashasaroy.uk
    • Bell Ribeiro-Addy — Labour Party — https://bellribeiroaddy.com
    • Mark Matlock — Reform UK — https://www.markmatlock.co.uk

  2. What the audit found

    On 7 September 2026 those URLs were requested again — 2 no longer resolved, 1 answered. An HTTP success means the server answered. It does not establish that the campaign page survived.

    • Bell Ribeiro-Addy — https://bellribeiroaddy.com — Answered (HTTP 200).
    • Asha Saroy — https://www.ashasaroy.uk — No longer resolved (DNS failure). An outage and a removal look the same in this check.
    • Mark Matlock — https://www.markmatlock.co.uk — No longer resolved (DNS failure). An outage and a removal look the same in this check.

  3. What happened to the words

    A homepage fetch was compared with the April site text for 1 of the 3 candidates here. A sentence missing from that fetch is not matched to a replacement.

    • Bell Ribeiro-Addy — 7182 sentences from the April text were not found on the homepage fetch of https://bellribeiroaddy.com. Example from the April text: “With most women suffering with Dysmenorrhoea at some stage and 1 in 10 women suffering from endometriosis, more attention needs to be given to solutions that…”

  4. Text overlap, where it was scored

    A separate Wayback comparison scored text overlap for some candidates. It kept the score and an archive URL.

    • Asha Saroy — Substantial text difference from the compared archived page against the 3 June 2024 archive. 21% of April tokens were still found. The capture sits outside the April 2025 scrape window. Sentence text for this comparison is absent from the snapshot. · Open the archive

No replacement sentence is matched. A line that only appears on the later homepage is listed on its own. 2 candidates on this seat have no sentence comparison in the snapshot.

Clapham and Brixton Hill — 1 of 3 sites responding (33%) · 2 unreachable · 0 redirectedHalftone: more / larger paper dots = lower response rate.

Candidates in this seat

Open filtered ledger — 3 sites ↗See what you followBrowse all 2,375 ↗UK overview ←

This link encodes the seat view · Press ⌘K to jump anywhere. This seat's hex is equal-weight (Automatic Knowledge v5, OGL) · How we checked →

Agent viewInspect the data and verify the record$0.002 / seat

Humans read this page for free. Agents pay per jurisdiction — this exact record is one metered call. Everything below is live; nothing here is mocked.

1 Free, same-origin

/api/constituencies/clapham-and-brixton-hill.json

Plain static JSON, CORS *, no key, 5-minute cache.

2 Metered via x402

https://civicord-aieyq.bazgateway.com/api/constituencies/clapham-and-brixton-hill

One jurisdiction = one charge. Expect 402, not an error.

3 MCP tool

Same call, as an agent would invoke it over MCP.

getConstituency(slug="clapham-and-brixton-hill")
-> { name: "Clapham and Brixton Hill", stats: { sites, live, livePct, ... }, candidates: [ ... ] }

4 The Graph (live)

On-chain p108264.civicord.eth via/api/graph (Studio proxy) — person id, not seat slug.

{
  candidate(id: "108264") {
    id ensName status url personName textRecordCount
    registeredAt registeredAtBlock owner
  }
  _meta { block { number } hasIndexingErrors }
}

Live queries run on demand; a failure is shown honestly, never replaced with a cached response. Verify independently: ENS ·resolver ·Subgraph Studio ·/api/graph ·openapi.yaml ·source

↑↓ move · ↵ open · Esc close