NVIDIACatProof is a member of NVIDIA Inception.Explore the program
catproof.
Get Started ↗
← All articles
AGENT ARCHITECTURE · 7 MIN READ

The B2A economy needs an agent system of record.

When software agents discover services and complete tasks, companies need a way to connect each source identity to a responsible owner and a reviewable decision.

·

In “Welcome to the B2A Economy,” Olivia Moore and Justine Moore argue that businesses will increasingly serve AI agents as customers. Their central shift is from agent-assisted discovery to agents that evaluate options and complete tasks. The traffic and adoption figures in that article are reported by a16z and its cited companies; they are not CatProof measurements.

That creates an operational question inside every participating company: which agent acted, under whose authority, using which integration, and what evidence supports that answer? A purchase log can show a transaction. A connector inventory can show an installed tool. Neither, by itself, identifies the accountable business owner of the agent that used it.

Map both sides of an agent transaction

A B2A interaction crosses two organizational boundaries. The customer-side agent receives a task and may call a browser or tool. The business-side service exposes pages, APIs, product data, and purchase flows. Each side may observe only part of the path.

A practical record should retain separate identifiers for the agent, its source platform, the connected tool, and the target service. Do not collapse an OAuth client, browser session, service account, and business agent into one identity merely because they appear in the same transaction. A token establishes a technical authorization path; it does not name the person accountable for the agent’s purpose or spending authority.

Use a durable record above source inventories

For an organization operating agents, the minimum useful model has four layers:

  1. Source observation: provider, configured scope, stable source identifier, collection time, and collection status.
  2. Identity link: an explicit association between a source identity and a durable business agent record, with evidence for the association.
  3. Business decision: accountable owner, purpose, lifecycle, and review notes, recorded independently from provider refreshes.
  4. Related assets: tools, service accounts, or endpoints connected through typed relationships when evidence supports the link.

CatProof’s system-of-record guide explains this separation. Its registry reads configured source inventories; it is not an organization-wide automatic discovery claim. The connector catalog gives the scope and validation status of each adapter.

A concrete reconciliation example

Suppose a fictional procurement agent appears in a development workspace as procure-assist and in production as purchase-helper. It uses a shopping connector and a payment service. A similar name would be weak linking evidence; a verified deployment reference or an operator decision can justify associating the two source identities with one business record.

{
  "business_agent_id": "agent-042",
  "purpose": "Compare approved office supplies",
  "accountable_owner": "Procurement operations",
  "source_identities": [
    {"platform": "configured-source-a", "scope": "dev", "source_id": "procure-assist"},
    {"platform": "configured-source-a", "scope": "prod", "source_id": "purchase-helper"}
  ],
  "relationships": [
    {"type": "uses-tool", "target": "shopping-connector", "evidence": "operator-reviewed"}
  ]
}

This is an illustrative data shape, not a CatProof API response or a production customer record. A source refresh might rename the production identity or report a different tool. That new observation should be retained without silently rewriting the owner, purpose, or earlier review decision.

Separate registration, authority, and execution

The registry can answer who is recorded as responsible and what sources were observed. Authorization and transaction controls remain at the systems that execute actions. For a purchasing workflow, those systems should enforce scoped credentials, spending limits, approval thresholds, and revocation. A CatProof lifecycle label such as “suspended” is a recorded decision; it does not stop an agent on its source platform.

Evidence also has a time boundary. A last-seen timestamp describes an inventory read, not live behavior. A failed or partial read should leave earlier observations marked stale rather than imply the agent has disappeared. An absent identity in one configured scope cannot prove deletion across an organization.

Questions to answer before an agent can buy

These questions turn the B2A thesis into an architecture requirement: keep source evidence and human decisions together in a durable, reviewable record. That record helps operators investigate agent activity and responsibility. It should not be presented as proof that a transaction was safe, compliant, or authorized unless the enforcement systems supply that evidence.

Sources and product scope

Moore and Moore, “Welcome to the B2A Economy” provides the market thesis. The architecture and operational recommendations here are CatProof’s analysis, not claims made by a16z.

CatProof product guide, connector coverage, and security and trust describe current product scope and limits. The example above is fictional.

Explore the fictional workflow ↗