Developers and agents

Start from the machine-readable files.

People can use the dashboard. Software agents should begin with the manifest and the runtime, then verify readiness before moving any funds.

Open the dashboard Open the explorer

Canonical files

Where an agent should look first.

Read /pob-agent.json.
Use window.SPAAdapter on the dashboard, or the headless bootstrap in /node_runtime.mjs.
Verify with payment-ready-check.

/pob-agent.jsonmanifest
/llms.txtsummary for LLMs
/skill.mdagent skill
/node_runtime.mjsheadless bootstrap
/cli.mjscommand line

Entry points

Three ways in.

Browser

await window.SPAAdapter.login({ userId, password });
await window.SPAAdapter.connectWallet(rpcUrl);
const contract = await window.SPAAdapter
  .getContractFromRegistry("venue merchant");
const wallets = await window.SPAAdapter
  .getSettlementWalletsForContract(contract.address);

Command line

node cli.mjs payment-ready-check \
  --user-id customer01 \
  --password 'customer-password' \
  --contract-name 'venue merchant' \
  --json

Headless JavaScript

import { setupNodeRuntime }
  from "./node_runtime.mjs";
await setupNodeRuntime();
const { createSPAAdapter } =
  await import("./adapter.js");

Getting payment-ready

Enroll a customer with a merchant.

Payment-ready means the merchant contract resolves in the registry, the token address and the merchant and fee owners are configured, and the customer's settlement wallet is linked. Funds and allowance are separate checks.

Connect the wallet

Select the merchant

Resolve the merchant contract from the registry and inspect its merchant and fee owner addresses.

Register with the merchant

Run merchantRegister(contractAddress) from the customer session to link a settlement wallet.

Verify readiness

Run payment-ready-check, then confirm funds and allowance before paying.

Want the full picture?

The whitepaper covers the design behind the runtime, including private chains, escrow, and agent payments.

Request the whitepaper Back to main