Start
Get started with Attesto
This guide gets a tenant from first login to a verified event without relying on generated content or temporary flows.
1. Sign in to the tenant dashboard
Use dashboard.attesto.eu. Tenant users manage their own systems, keys, Proofstream views, exports, billing, webhooks, and connectors there.
2. Register a system
Open Settings -> Systems, create a system for the production service that will send events, and copy the generated system key when it is shown. The key is displayed once and must be stored in your server-side secret manager.
3. Log the first event from server-side code
SDK defaults point at https://verify.attesto.eu. Do not
embed Attesto system keys in browser bundles, mobile apps, client
logs, or client-visible environment variables.
python - <<'PY'
import os
from attesto import AttestoClient
attesto = AttestoClient(api_key=os.environ["ATTESTO_API_KEY"])
ack = attesto.log_event(
type="inference",
status="verified",
payload={"model": "risk-service-v4", "decision": "review"},
)
print(ack.id)
PY
4. Verify evidence
For v1 anchored events, retrieve the event proof and submit it to the
public verifier. For v2 Proofstream, verify receipts, streams,
checkpoints, and bundles through the SDK helper or the
POST /v2/verify API.
5. Export for an auditor
In the dashboard, create an evidence export for the required date range. Attesto bundles include verifiable material and must be treated as immutable evidence files once shared.
Production rule
A green first event means the API path works. Production evidence readiness still depends on tenant policy, witness/quorum settings, anchoring cadence, retention, and export controls for your use case.
