A coherent .com category set for the permission-and-proof layer of AI agents, compute, and enterprise automation — priced for the EU AI Act compliance window (fully applicable August 2, 2026).
Bundle available
Buy the Permits & Receipts domain bundle.
This cluster can be bought as one coordinated set: permission names for what AI systems may do, and receipt names for the proof they leave behind.
The Permits names address authorization (what an agent or system is allowed to do). The Receipts names address evidence (proof of what happened). Together they form a complete category set for AI governance product builders.
Bundle pricing available for the full seven-domain set — use the bundle inquiry button above or below.
Domain detail
Each name, priced and positioned.
Hover or tap any name in the summary above to jump to its detail card.
Permits Cluster
ToolPermits.com
The Category Name for AI Agent Tool Authorization
Premium two-word .com for the emerging AI agent permissioning category. As AI agents move from demo to production, every agent action through a tool — APIs, browsers, payment rails, internal systems — needs a permission layer. ToolPermits.com is the natural category name for that layer, sitting alongside identity (Auth0, Stytch, WorkOS) and agent infrastructure (Arcade, Nango) buyers actively building in this space.
Suggested Use Cases
AI agent authorization platform
Tool-call permissioning SaaS
Enterprise agent governance product
Non-human identity (NHI) permissions
MCP server access control
Permits Cluster
ComputePermits.com
Regulatory-Ready Compute Authorization Brand
Category .com for compute access governance under emerging AI regulation. Under the EU AI Act (fully applicable August 2, 2026) and parallel U.S. frameworks, frontier compute access is becoming a regulated permission. ComputePermits.com positions a product directly inside the governance, audit, and compliance buyer pool — Credo AI, Holistic AI, Fiddler, OneTrust — and is a clean naming fit for sovereign compute allocation platforms.
Suggested Use Cases
AI compute governance platform
Frontier model access licensing
Sovereign compute allocation
Compute audit and compliance SaaS
AI infrastructure regulatory reporting
Permits Cluster
AgentPermits.com
Permissions Layer for Autonomous AI Agents
The companion category name to ToolPermits, scoped at the agent identity level. Every autonomous agent needs scoped permissions to act on a user's behalf. AgentPermits.com is the natural product name for that layer — directly applicable for Stytch, WorkOS, Arcade, Auth0, Nango, and Noma Security as they build agent-native permissioning. Strong companion asset to ToolPermits.com.
Suggested Use Cases
Agent identity and permissions platform
Scoped delegation for AI agents
Non-human identity governance
Agent OAuth and authorization layer
Receipts Cluster
IntentReceipt.com
Proof of Intent for AI Agent Actions
Category .com for the audit-trail layer every AI agent product now needs. With Avinash Lakshman publicly launching "Receipts for Claude.ai and ChatGPT" in February 2026, "Receipts for AI" is now a real product category. IntentReceipt.com is the cleanest category name for verifying user/agent intent, approval flows, and policy context — directly relevant for tamper-evident provenance vendors (Kevros), AI safety platforms (Lakera, Robust Intelligence), and observability buyers (WhyLabs, Arize).
Suggested Use Cases
AI agent intent verification
Tamper-evident decision logging
Audit-ready approval trail SaaS
Policy context evidence layer
Regulatory disclosure for AI decisions
Receipts Cluster
ControlReceipt.com
Evidence Layer for Enterprise AI Controls
Category .com for proving policy and control execution on AI and automated actions. Every enterprise AI deployment now requires evidence that controls fired, approvals were checked, and policies were applied — for SOC 2, ISO 42001, and EU AI Act audits. ControlReceipt.com is the natural product name for that evidence layer. Direct fit for compliance platforms (OneTrust, Drata, Vanta, AuditBoard) and AI governance vendors (Credo AI, Holistic AI).
Suggested Use Cases
AI controls evidence platform
Compliance audit log SaaS
ISO 42001 / SOC 2 AI evidence
Policy execution proof
Receipts Cluster
RuntimeReceipt.com
Execution Evidence for AI Systems
Technical category .com for AI runtime governance and execution trails. As AI moves from research artifacts to production runtimes, every inference, tool call, and policy decision needs an evidence trail. RuntimeReceipt.com is the natural product name for runtime governance — directly applicable for AI observability (Arize, Fiddler, WhyLabs) and runtime security buyers.
Suggested Use Cases
AI runtime governance
Inference evidence and audit
Policy-decision logging SaaS
AI observability evidence layer
Receipts Cluster
ToolReceipt.com
Proof Layer for AI Agent Tool Calls
The companion Receipt name to ToolPermits — permission plus proof. Every tool call from an AI agent should produce a receipt: what was called, by whom, under what policy, with what result. ToolReceipt.com is the category name for that evidence layer, sitting directly alongside ToolPermits.com as a permission-and-proof pair. Best sold as a bundle, but stands alone for any agent infrastructure or observability buyer.
Suggested Use Cases
Agent tool-call evidence
Tool-use audit trail SaaS
Companion proof layer for permissions
Agent forensics
Why now
The compliance window is the urgency.
The EU AI Act becomes fully applicable on August 2, 2026. Parallel U.S. frameworks (NIST AI RMF, SOC 2 AI guidance, ISO 42001) are forming around the same primitives: who authorized this action, what evidence proves it happened. The product category that solves both — permits and receipts — is being built right now by named vendors.
The window to acquire a category name before consolidation is typically 9–12 months from the regulatory trigger. We're inside it.