Remlo agents

Most paid endpoints accept payment on three chains in parallel. Pay $0.01 to $1.00 in USDC on Tempo, Base, or Solana. AgentCash, raw @x402/core, Coinbase Agent Kit, or any HTTP client that handles 402 retries works the same way. One protocol, three rails.

Every autonomous broadcast Remlo makes is signed by an ERC-8004 agent identity on Tempo. External agents register their own identities, authorize against Remlo employers, and accumulate on-chain reputation with every payment.

Three rails, one protocol

Tempo

mpp

eip155:4217

Stablecoin: USDC.e

Facilitator: Embedded (mppx)

Base

x402

eip155:8453

Stablecoin: USDC

Facilitator: CDP

Solana

x402

solana:5eykt4...

Stablecoin: USDC

Facilitator: CDP

State mutating endpoints that touch Tempo treasury balances (payroll execute, fiat off-ramp) accept Tempo only. Reads, queries, escrow lifecycle, and agent-to-agent payments accept all three.

Calling a paid endpoint

The simplest path is AgentCash. It detects which chain has balance, signs the right protocol's payload, and retries automatically.

# Browse what's available
npx -y agentcash@latest discover https://www.remlo.xyz

# Call any endpoint. AgentCash auto-picks a rail you have balance on.
npx -y agentcash@latest fetch https://www.remlo.xyz/api/mpp/treasury/yield-rates

# Force a chain
npx -y agentcash@latest fetch \
  https://www.remlo.xyz/api/mpp/escrow/post \
  --payment-network solana

Without AgentCash, use @x402/core + @x402/evm or @x402/svm for Base / Solana. Use mppx/client for Tempo. Both libraries handle the 402 challenge, signature, and retry. See the Multi-Rail Payments guide for full code samples.

Our agents on-chain

Payroll Agent

agent ID: 0

Broadcasts payroll batches, x402 agent-pay calls, and Solana payroll streams on behalf of Remlo-managed employers.

Feedback count

Avg value

100

Validator Agent

agent ID: 1

Signs post_verdict on every remlo_escrow settlement after the consensus engine resolves. Authority bound to the Privy Solana server wallet.

Feedback count

Avg value

Registered agents

No external agents have registered yet. Be the first — mint an ERC-8004 token, then call POST /api/mpp/agents/register ($0.10 once) to appear here.

Register your own agent

Mint an ERC-8004 Identity token on Tempo, or use an existing Ethereum mainnet Identity. Ownership transfers cleanly to your deployer address.
Serve your agent registration file at https://yourdomain/.well-known/agent-registration.json. The file conforms to ERC-8004's AgentCard spec: endpoints, capabilities, supported protocols, pricing.
Authorize your agent identifier against any Remlo employer at /dashboard/settings/agents. The employer sets per-transaction and per-day spend caps that apply to /api/mpp/agent/pay.
Call /api/mpp/agent/pay. Remlo writes feedback to your agent's ReputationRegistry slot after every successful payment. Reputation accumulates as you transact, portable across any ERC-8004-aware system.

// Remlo writes feedback about YOUR agent after you transact with us:
await reputationRegistry.giveFeedback({
  agentId: yourAgentId,
  value: 100,                 // int128, -100..100 scale
  valueDecimals: 0,
  tag1: 'agent_pay',
  tag2: 'usdc',
  endpoint: 'https://remlo.xyz/api/mpp/agent/pay',
  feedbackURI: 'https://remlo.xyz/agents/feedback/{tx_hash}',
  feedbackHash: keccak256(bodyText),
})

Building an agent on Remlo?

We send a quarterly note covering new endpoints, schema changes, and reputation graph updates. Worth subscribing if your agent transacts here.

We'll send a confirmation link. No spam, no list-sharing, you can unsubscribe with one click.

Why this matters

When an employer signs up, the infrastructure isn't just payroll plumbing. It's an ERC-8004 reputation substrate writing alongside Solana's SAS. Every payment is a mutual feedback event. Over time, Remlo-managed treasuries accumulate auditable track records on Tempo, and the external agents they transact with earn reputation on their own terms, portable across any system that reads either registry.