Documentation

Inficy records what an AI agent did and lets you read it back: connect an agent, executions appear, you inspect them, and you can export, verify or optionally certify a selected execution. This page is server-rendered and readable without JavaScript. The exact, ready-to-paste command for your workspace is generated inside the app on the Connect agent screen.

Start here

1. Connect an agent, one command, no manual secret handling.
2. Read executions, activity, timings, tools, domains, handoffs, failures and outcomes.
3. Work with evidence, verification, export and confidential executions.
4. Certify when needed, optional, per execution, paid in credits.

Connect an agent

1. Create a workspace and open Agents → Connect agent.
2. Generate a setup code. It starts with ifc_setup_ and expires in 10 minutes.
3. Paste the generated command into your coding agent or run it in the project.
4. The installer exchanges the setup code for a permanent reporting token, stores it as a secret, and runs a connection self-check.
5. The workspace reaches Ready only after a real test artifact passes verification.

Redemption endpoint

POST /api/public/v1/agent-connections/redeem is a machine-to-machine endpoint. It requires no browser session and no user JWT, the one-time setup code is the authentication. It always responds with JSON and never redirects to an HTML sign-in page. Errors are structured: 401 for an invalid code, 409 for an already-redeemed code, 410 for an expired code.

Ingestion endpoint

POST /api/public/ingest accepts a canonical NexArt artifact together with an idempotency key, authenticated with the permanent reporting token. Requests are validated against a strict schema, size-capped, rate-limited per workspace and queued for background processing. Re-sending the same idempotency key is safe and never duplicates history.

Evidence and verification

Every artifact is verified offline with the NexArt SDK against its Project Bundle before it is trusted. Verification is not certification: verification proves the artifact is internally consistent and unaltered, certification adds an independent attestation from the NexArt Node. An execution that failed is not the same thing as an artifact that failed verification, and the two are displayed separately.

Machine interfaces

Machine callers have their own reference surfaces: /llms.txt and /llms-full.txt for language models, /openapi.json for the REST API, /.well-known/agent-card.json for A2A discovery and the MCP endpoint at /mcp for assistants that speak MCP. Every credential is bound to one workspace and an explicit scope set; read never implies write, and spending always requires an owner-signed mandate.

Next

Read how Inficy works, the security model, or the frequently asked questions.