API
Call api.affix-io.com with a Hub key. The contract is OpenAPI, not a blog post.
OpenAPIIntegrations
Sit beside the stack you already run.
API, Hub, signed webhooks, evidence export, and the public tools. No rip-and-replace of the systems that hold the file.
SDK
Wire from Node with affixio. Prove on the host that holds the record.
affixioWebhooks
Signed pushes when a proof is created, verified, spent, anchored, or a key is revoked.
WebhooksEvidence export
NDJSON or JSON for GRC and log pipelines. Use this when you need a complete record, not only a push.
SIEMAgents
llms.txt and the agent page are the citation surface. Do not scrape a mailbox.
For agentsHub
Register webhook URLs, rotate secrets, issue keys.
Sign InIntegration is a buying question
The objection is never the yes or no. It is whether webhooks, export, and keys fit the SIEM and GRC path you already operate.
API
Call api.affix-io.com with a Hub key. The contract is OpenAPI.
OpenAPIWebhooks
Signed pushes when a proof is created, verified, spent, anchored, or a key is revoked.
WebhooksExport
NDJSON or JSON for GRC and log pipelines when a push is not enough.
SIEMAgents
llms.txt is the citation surface. Do not scrape a mailbox to invent product behaviour.
For agentsIntegration questions
Do I need two Node packages?
No. Use affixio.
Where do webhook secrets live?
In Hub, per endpoint. Rotate there if one leaks.
Can I poll instead of webhooks?
Yes. Webhooks are for latency. Export is for completeness.
How does AffixIO integrate?
HTTPS API, affixio on the host, signed webhooks, and NDJSON export. No rip-and-replace of the systems that hold the file.
Webhooks vs export?
Webhooks for latency. Export for completeness.
Where do secrets live?
In Hub, per endpoint. Rotate there if one leaks.