Civicord · UK · Browse / Chippenham

Chippenham · E14001168 · South West · England · 71,648 electorate

Chippenham

Mixed HTTP results — The rounded HTTP response rate at the audit was between 40% and 65%. Inspect each URL for its result. 1 of 2 sites responding (50%) · 0 unreachable · 1 redirected

What happened here

  1. What was recorded

    The April 2025 scrape recorded 2 candidate websites for Chippenham.

    • Nic Puntis — Conservative and Unionist Party — https://www.nicpuntis.uk
    • Ravi Venkatesh — Labour Party — http://way2ravi.com

  2. What the audit found

    On 7 September 2026 those URLs were requested again — 1 redirected, 1 with another HTTP result. An HTTP success means the server answered. It does not establish that the campaign page survived.

    • Ravi Venkatesh — http://way2ravi.com — Audit result: HTTP error (HTTP 500).
    • Nic Puntis — https://www.nicpuntis.uk — Redirected to https://www.conservatives.com/. The surname was not in the response body.

  3. What happened to the words

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

    • Nic Puntis — 256 sentences from the April text were not found on the homepage fetch of https://www.nicpuntis.uk. Example from the April text: “Nic’s involvement in the hospitality industry, owning Sarah-Jaynes Café and being involved in the running of Soho Public House in Derry Hill, has helped him…”

  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.

    • Nic Puntis — Substantial text difference from the compared archived page against the 11 April 2025 archive. 21% of April tokens were still found. 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. 1 candidate on this seat has no sentence comparison in the snapshot.

Chippenham — 1 of 2 sites responding (50%) · 0 unreachable · 1 redirectedHalftone: more / larger paper dots = lower response rate.

Candidates in this seat

Open filtered ledger — 2 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/chippenham.json

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

2 Metered via x402

https://civicord-aieyq.bazgateway.com/api/constituencies/chippenham

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

3 MCP tool

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

getConstituency(slug="chippenham")
-> { name: "Chippenham", stats: { sites, live, livePct, ... }, candidates: [ ... ] }

4 The Graph (live)

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

{
  candidate(id: "81212") {
    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