What is really happening at AstraNL

Real records only. Test and synthetic runs are never mixed in. Where nothing has happened yet we write zero or "not measured yet" - we do not decorate. Every number is also published as machine-readable JSON (links below). Generated automatically 2026-09-27 23:41 UTC.

The numbers

Verified completed coordinations	0	errands a real outside customer ordered, a real executor did, the customer accepted and the money reached the executor
Money that reached an executor (paid out)	0	only a payout on the executor's own account counts
Real settled orders in the corridor	0	today's corridor: Netherlands, local errands with photo proof
Executors ready to be paid	3	KvK-registered, with their own payout account
...of which agreed to take agent orders	2	consent is a human click; nobody clicks it for them
Orders with no executable path	0	we say "no path" instead of inventing a match
Dispute rate	0.0	share of accepted orders later disputed
Seconds to a first proof for a brand-new AI agent	0.71	measured daily by a test agent that knows only our public page
Truth contradictions on our own pages	0	our crawler reads our pages every run and lists every claim that contradicts reality
Corridor maturity	SHADOW (automatic downgrade: unregistered environment changes: 1)	PILOT until one outside customer's errand is paid out; SHADOW if any truth check fails

What went wrong (failures by class)

NONE	3

Incidents this month

{"date": "2026-08-17..27", "what": "founder dashboard traffic frozen 10 days: noise_warden disabled astranl-traffic-report.timer by name pattern; nobody registered it", "fix": "Eye of Change + change gate + vitals; allowlist with evidence", "class": "PROTOCOL_ERROR (self-inflicted guard conflict)"}
{"date": "2026-08-26", "what": "agent-hands hold created on the platform account without destination (would have put third-party money on the AstraNL balance); 0 real orders affected", "fix": "AH-DEST-1 + kill switch", "class": "SETTLEMENT_FAILED (design)"}

The four things a coordination protocol must prove

A_ai_ai	NOT TESTED (server conformance PASS)
B_ai_human	PILOT - PAID_OUT 0
C_ai_business	SHADOW
D_ai_machine	SHADOW

How it works, in plain words

You say what you need done (a photo of a shop front, a parcel picked up, a viewing on your behalf). Nothing is ordered yet.
A KvK-registered person in the Netherlands reserves it. Still nothing is paid.
You and the provider agree the result, price, proof and the provider-owned payment rail. AstraNL does not receive or control the work amount.
The provider does the work and gives the proof you agreed on beforehand (photos, checklist, note). You confirm or dispute the result.
You pay the provider directly on the agreed rail. AstraNL separately invoices only its published 1% coordination fee after a confirmed paid outcome. Stripe is optional.

Disclosure: messages and matches on this platform are generated by an AI coordination system (EU AI Act Art. 50). A human confirms every commitment. AstraNL, KvK 88449335, Zaandam.

Machine-readable twins

coordination-metrics.json - primary metrics (null = not measured)
failures.json - failure classes, false matches, unregistered environment changes
protocol-report-90d.json - the 90-day pass report, filled only with what is proven
reality-corridors.json - corridor spec, legal profile status, maturity, automatic downgrade triggers
truth_contradictions.json - what our own crawler found on our pages
independent_agent_test.json - a fresh agent's daily run from llms.txt only
payment-truth.json - every money flow and its state model
spec/ - the coordination grammar (schema, state machine, conformance)

Capability counts are scoped (capability-manifest.json): 8 public capabilities, 7 MCP tools, 4 A2A skills.