Roadmap
This page is the honest list of what is not yet shipped. Every item is planned, not available. The goal is simple: the documentation describes what exists, and this page gathers what does not yet exist, so you never confuse the two. This state reflects the current reality and may change; the order and scope are not commitments.
Do not build against these until they ship
Nothing on this page is callable, guaranteed, or stable today. Do not code against an endpoint, field, or network listed here before it appears in the reference documentation as shipped. If you need one of these capabilities, talk to us rather than assuming it is present.
Reading a customer through /v1/customers
Not available. The customer listing and per-person record are dashboard-only
today (see Customers). There is no public API to
list or read customers programmatically. The only /v1 endpoints under
/v1/customers/ are the two relationship-lifecycle actions (relationship/end
and relationship/revert, scope relationship), and neither exposes any customer
data. A read surface is planned; any programmatic flow must for now go through the
dashboard and the portability export.
A server receipts/verify path
Not available. On a citizen receipt, the company-signature check is
unsupported offline: the receipt omits the original offer fields to preserve
unlinkability, so a sound check needs a server receipts/verify endpoint. That path
does not exist yet. This is precisely why a citizen receipt honestly caps at
partial offline today (see Verify a receipt). A
company-attested receipt, by contrast, already verifies fully offline.
Outbound webhooks
Not available. There is no outbound event delivery today: no webhook when a
request is approved, refused, or expires, nor when a consent is revoked. You must
poll (for example waitForSettlement or agreely request wait). Webhook event
delivery is planned.
The company did:web served from its own /.well-known
Not available. Today the company's did:web document is hosted by Agreely,
at did:web:agreely.ca:c:{slug}. Serving the did:web from the company's own
/.well-known, on its own domain, is planned but not yet possible. Verifiers must
for now resolve the company DID through the Agreely-hosted host.
Shipped since: Base mainnet anchoring
This page used to list mainnet anchoring as not deployed. That is no longer true: since 12 August 2026, production anchors are written to Base mainnet (chain id 8453). See the on-chain registry for the contract address and the explorer link.
Next
- API reference: the
/v1surface as it exists today. - What Agreely is: what the protocol already ships.