AI agent integration and protocol engineering

Technical notes by Jason Colapietro on AI agent integration, x402 payments, agent identity and tool execution. Use these explainers to evaluate the protocols behind the Suede AI stack, then explore the product documentation or discuss an integration.

From workflow to integration

Start with the workflow, the systems it touches and the decisions that need human approval. The explainers here cover agent payments, identity and tool execution. They help a team evaluate the protocol choices behind an integration; the professional engagement is described on Jason Colapietro’s site.

Engineer first

The public engineering record includes merged contributions to Jest, Backstage and the Polkadot SDK. The linked contribution ledger separates substantive code and documentation from accepted project listings; the public Linux kernel USB/IP submission is tracked separately from merged pull requests.

What this site is

Plain-language technical explainers for the protocol layer of the Suede stack. Written so that a developer can decide in five minutes whether a protocol fits, and a founder can understand why it was chosen.

Four rails, one stack

The protocol layer splits into four jobs. x402 moves the money: a server answers HTTP 402 with a price, and the agent pays and retries in the same request cycle. ERC-8004 carries identity, so a paying agent can check who it is dealing with. The Agent Commerce Protocol covers the negotiation in between, from request to escrow to evaluation. Conduit enforces the three at runtime by checking identity, permission and payment before a skill call executes.

What is running

Suede AI Agent Studio lets a builder draw an agent as a node graph and launch it as an x402 pay-per-call endpoint that settles in USDC on Base. Agentix tracks what each launched agent earns, call by call. The stack implements x402 and ERC-8004, and a fix from this work is merged in the x402 Foundation's own repository.

Protocol explainers

Each protocol has a full explainer on the Suede performance site.

x402: the rail agents actually pay onHow x402 payments work over HTTP 402, which signals count toward x402 readiness, and what buyer agents need to pay you in USDC.
ERC-8004: trustless agent identityHow ERC-8004 agent identity works and how it is verified onchain: registry pinning, the agentURI round-trip and Trust / Proof points.
What is ACP? (Agent Commerce Protocol)How the Agent Commerce Protocol works, from request to escrow to evaluation, and the manifest checks behind the ACP score.
Conduit: the execution layerConduit checks identity, permission and payment before an agent skill runs. The open standards behind each check, and what a fail-closed check looks like.

Build, ship and check

x402 Agent Builder: Get Paid Per CallBuild an AI agent on a visual canvas, set a price per call, and get paid in USDC on Base through x402 once you enable payments. Dry runs need no wallet.
Agentix: x402 AI Agent Earnings Tracker for USDC on BasePer-call earnings for every agent launched from Agent Studio.
Suede AI Developer Docs: x402 APIs and Creator IPDeveloper docs for programmable IP, creator ownership, provenance, licensing, and x402 agent-commerce APIs, with the canonical GitHub source.
Agent commerce in the accomplishments recordThe dated record for Agent Studio and Agentix, with a link to the merged x402 Foundation pull request.