Plug agent identity into your stack.

AgentKit ships the wallet and the x402 payment rail — Agentic Wallets, TEE-enforced, wired into OpenAI Agents SDK, LangChain, MCP, and the Vercel AI SDK — but no VC/DID layer. The Solidus adapter issues did:solidus and a BBS+ credential into any AgentKit wallet in one call, turning a Coinbase agent wallet into one a regulated relying party will accept. We don't compete on x402 — the BBS+ proof rides in the request header of an x402-gated call.

import { createAgentIdentity } from '@solidus-network/agent-identity';
import { withSolidusIdentity } from '@solidus-network/agent-identity/agentkit';
import { AgentKit } from '@coinbase/agentkit';

const solidus = createAgentIdentity({ baseUrl: 'https://agents.solidus.network', token });
const wallet = await AgentKit.from({ cdpApiKeyName, cdpApiKeyPrivateKey });

const { agent } = await withSolidusIdentity(solidus, wallet, { capabilities: ['browse'] });

// agent.solidus.did → did:solidus:testnet:5dK3…tHgAs
// the BBS+ credential rides in the x402 request header

Every adapter on this page wires Solidus into an agent's build step. @solidus-network/mcp wires it into the agent's run-time instead — a standard MCP server exposing resolve_did, verify_credential, check_mandate, create_mandate, and agent_pay as ordinary tool calls. Point any MCP client (Claude Code, Cursor, Windsurf) at it over stdio and your agent can resolve a did:solidus DID, verify a credential, and check a spend mandate with no SDK code at all. agent_pay authorizes a payment under a mandate and hands back the envelope for the agent's own rail — Solidus never settles the money.

1{
2  "mcpServers": {
3    "solidus": {
4      "command": "npx",
5      "args": ["-y", "@solidus-network/mcp"]
6    }
7  }
8}

Crossmint's MiCA-authorized custodial wallets already handle agent KYC/AML/Travel Rule across 50+ chains — but the check is bound to their custody, and re-charged per relying party. The Solidus adapter binds a Crossmint-managed agent wallet to a did:solidus passport: a portable credential the operator carries across platforms, not one locked inside a single custodian.

1import { createAgentIdentity } from '@solidus-network/agent-identity';
2import { withSolidusIdentity } from '@solidus-network/agent-identity/crossmint';
3
4const solidus = createAgentIdentity({ baseUrl: 'https://agents.solidus.network', token });
5
6const { agent } = await withSolidusIdentity(solidus, {
7  walletLocator: crossmintWallet.locator,
8});
9
10// agent.solidus.did resolves to the same portable passport,
11// independent of Crossmint's custody

Olas runs agent execution across Gnosis, Base, and Optimism with no identity layer of its own. The Solidus adapter issues credentials to Olas autonomous services and anchors them to ERC-8004 — a clean compose-with at a different layer: Olas runs the agent, Solidus proves who it is.

1import { createAgentIdentity } from '@solidus-network/agent-identity';
2import { withSolidusIdentity } from '@solidus-network/agent-identity/olas';
3
4const solidus = createAgentIdentity({ baseUrl: 'https://agents.solidus.network', token });
5
6const { agent } = await withSolidusIdentity(
7  solidus,
8  { serviceId: 'olas:gnosis:0x9F1a…' },
9  { capabilities: ['task:execute'] },
10);
11
12// agent.solidus.did → did:solidus:testnet:5dK3…tHgAs
13// agent.solidus.passport → ERC-8004 anchor { chainId, tokenId }

OriginTrail is an explicit ERC-8004 partner — we mirror their published ERC-8004 + DKG integration template. This isn't an agent-registration adapter; it's a knowledge layer bridge. Solidus credentials are cross-published as DKG knowledge assets for agent provenance, reaching OriginTrail's Trace Alliance network.

1import { publishKnowledgeAsset } from '@origintrail/dkg.js';
2
3await publishKnowledgeAsset({
4  content: { agent: agent.did, capability: credential.id },
5  epochsNum: 2,
6});
7
8// → UAL cross-references did:solidus:testnet:5dK3…tHgAs

Every BBS+ credential Solidus issues is also dual-emitted as an EAS attestation with the identical payload, under a Solidus issuer schema published to the EAS public registry. That turns EAS from a silo into a discovery surface — EVM-native consumers like Verax and Karma3 see Solidus credentials with zero Solidus integration.

1import { EAS } from '@ethereum-attestation-service/eas-sdk';
2
3const attestation = await eas.getAttestation(easUid);
4
5// → same claims as the BBS+ credential, discoverable via
6//   EAS's public registry — no Solidus integration required

Compose-with for agent payments — targeted Q4 2026. Not yet available. When it ships, the adapter will let a Privy-embedded wallet carry a Solidus credential into an x402-gated payment the same way the AgentKit adapter does today.