Overview
FreeNo activity yet
No signed receipts yet
Follow these 5 steps to sign your first action.
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.
No activity yet
No signed receipts yet
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 enforcement decisions yet
Enforcement decisions appear here when agents gate tool calls through the Asqav SDK. Install with pip install asqav and wire the asqav hook CLI into Claude Code.
No policies yet
Policies enforce rules on agent actions
Incidents are available on Enterprise
Track, investigate, and resolve security incidents
No incidents yet
Incidents are created from alerts or manually reported
No compliance reports yet
Generate your first EU AI Act, DORA, or SOC 2 report
No proofs yet
Cryptographic proofs appear here once your agents start signing actions.
No multi-party signing configured yet
Define who needs to approve agent actions and how many approvals are required.
Approvals are included in your plan
Hold high-risk agent actions for human review
No approval requests
When an agent action is held for human review, it appears here with full context.
Permanently delete your account and all associated data.
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
Restrict 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
Every signature includes a legally-compliant RFC 3161 timestamp, signed with ML-DSA-65 per RFC 9882.
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.
No Shadow AI captures yet
Deploy the egress shim to surface network-proxy captures. See the docs.
Hi! I can help you navigate the dashboard and find information about your agents, activity, and alerts.