Overview
Latest recorded actions
View evidenceNo signed receipts yet. Connect an agent to record your first action.
Recent workspace changes
No activity yet
Usage and signing performance
Signing time: last 24 hours. Usage and spend: this month.
Connect an agent to start collecting signed evidence. Share the integration guide with your engineering team. View integrations
pip install asqav
export ASQAV_API_KEY=<paste your key here>
import asqav
asqav.init()
agent = asqav.Agent.create("my-first-agent")
receipt = agent.sign("test", {"hello": "world"})
print("Receipt:", receipt.verification_url)
The printed link is your signed receipt, verifiable by anyone without an API key. Refresh this page to see the agent and its signed action below. If nothing shows up, email info@asqav.com.
Loading recorded activity…
No signed receipts yet. Connect an agent to record your first action.
No activity yet
Signing time: last 24 hours. Usage and spend: this month.
No agents yet
Agents are created by the SDK. Open the Overview quickstart to create your API key and run the first snippet.
No activity yet
Activity is recorded when agents perform actions
No action decisions yet
Decisions appear when a connected agent checks an action against your rules. Connect an agent.
No policies yet
Policies enforce rules on agent actions
Repeated policy violations can suspend or quarantine an agent’s access to Asqav. Manage its current status in Agents.
Review reported issues and record how they were resolved
Incidents are available on Enterprise
Track, investigate, and resolve security incidents
No incidents yet
Incidents are created from alerts or manually reported
Generate and download evidence reports for an audit.
No compliance reports yet
Generate your first EU AI Act, DORA, or SOC 2 report
No signed evidence yet
Timestamp proofs appear here after signed actions are anchored.
Monitor requests that need several signers. Your integration collects the signatures. Setup guide
Manage an existing integration’s keys and signing rules. For a person’s review of recorded evidence, use Approvals.
No multi-party signing configured yet
Start with the integration guide to configure signer groups and key custody.
Approve or deny requests Guide
No approval requests
Your integration can submit an existing signed record or daily proof for human review.
Permanently delete your account and all associated data.This action cannot be undone.
Add an extra layer of security using an authenticator app.
Sign in with a linked provider instead of your password.
API keys are used to authenticate SDK requests.
No API keys yet
API keys authenticate SDK requests. Create one to start signing actions.
Export traces to observability platforms (Datadog, Honeycomb, Jaeger). Set OTEL_EXPORTER_OTLP_ENDPOINT env var.
Store ML-DSA signing keys in AWS KMS or Google Cloud KMS with HSM protection. Set KMS_PROVIDER=aws or KMS_PROVIDER=gcp env var.
Webhooks are included in your plan.
Send alerts to Slack, Discord, Microsoft Teams, or any webhook endpoint.
No webhooks yet
Webhooks receive alert notifications when events occur
Pick the regimes your organization claims to follow. Audit-pack exports include these tags.
No team members yet
Invite collaborators to share this organization.
No pending invitations
Invitations you send appear here until accepted.
IP Allowlist and SAML SSO are available on Enterprise plans. Contact info@asqav.com
For integrations that require several signers. Set up through the API.
View signingRestrict API access to specific IP addresses or CIDR ranges.
No IP restrictions yet
IP restrictions limit API access to specific addresses
Enable single sign-on with your identity provider (Okta, Azure AD, etc).
SAML not configured
Click Configure to set up SSO
Receipts include cryptographic signatures. Inspect each receipt for its timestamp and verification evidence.
ML-DSA-65 (FIPS 204)
Timestamps are automatically added to all signatures.
Store ML-DSA keys in your own AWS KMS or GCP KMS account. FIPS 140-3 Level 3 compliant. Enterprise tier.
Environment Variables
KMS_PROVIDER=aws
AWS_REGION=eu-west-1
AWS_ACCESS_KEY_ID=your-key
AWS_SECRET_ACCESS_KEY=your-secret
Contact info@asqav.com to enable BYO KMS for your organization.
No support tickets yet
Open a ticket if you need help from the Asqav team.