Record entry · Defense Procurement

Project Agincourt

What is happening now

Cannot measure: the record's node for this name could not be read, so its claims are not known here.

How well we know this

Cannot measure: No entity labelled "project-agincourt" in the record at 2026-10-21T13:12:56.354446+00:00. Try search_entities, or GET /api/signals..

Added 21 Oct 2026Mentions 31Sources 17Days of coverage 11

Why this name is on the record

Project Agincourt was added automatically on 21 Oct 2026 after 31 mentions across 17 sources over 11 days. 58% of that coverage came from a single subject area.

Reported alongside Project Agincourt

The neighbourhood is not yet read for this page.

For developers

GET https://api.signalbureau.ai/api/registry?slug=project-agincourt

{
  "slug": "project-agincourt",
  "state": "active",
  "detail": {
    "state": "active",
    "source": "ontology",
    "label": "project agincourt",
    "promotedAt": "2026-10-21",
    "category": "defense_procurement",
    "evidence": {
      "mentions": 31,
      "sources": 17,
      "days": 11,
      "concentration": 0.581,
      "standAloneShare": 1
    }
  }
}

The record behind this page, as data. The live response also carries the registry date and version.

Walk the record from Project Agincourt

This name is not in the walkable record yet: the entity graph does not carry it at this cutoff.

The coverage behind it

Ask about Project AgincourtWatch Project Agincourt

No trend and no market price are shown because neither has been measured for Project Agincourt yet. Informational only, not advice. As of 21 Oct 2026.