Integrations
OOBE Protocol

OOBE Protocol

OOBE Protocol powers autonomous AI agents on Solana via the Synapse Agent Protocol (SAP). Concierge is an intel provider — pay-per-call desk verdict and Meteora DLMM data before your agent executes on-chain actions. Settlement uses x402 USDC (PayAI facilitator). No Concierge API key required.

Status: Live — SAP manifest, agt_ ↔ SAP linking, OOBE settlement adapter

Origin: https://conc-exe.xyz

OOBE: oobeprotocol.ai ↗

SAP docs: explorer.oobeprotocol.ai ↗

Manifest: sap-tools-manifest.json

Agent skill: concierge-oobe/SKILL.md

How it works

  1. Your OOBE agent (Synapse Studio or SAP CLI) needs market intel before a swap, LP, or stake action.
  2. Call a Concierge tool — concierge:intel-verdict or concierge:intel-meteora — from the SAP manifest.
  3. Agent wallet pays $0.10 USDC per call via x402 (PAYMENT-SIGNATURE header, PayAI facilitator).
  4. Branch on verdict.signal (snipe · watch · avoid) or Meteora pool data, then run your on-chain action.

Concierge uses PayAI/Dexter facilitator x402 today — not SAP escrow headers. Use pay curl or SAP CLI with --endpoint override (see below).

SAP tools (phase 1)

SAP tool idEndpointUSDC
concierge:intel-verdictPOST /api/concierge-intel-verdict$0.10
concierge:intel-meteoraPOST /api/concierge-intel-meteora$0.10

Full manifest: /distribution/oobe/sap-tools-manifest.json

Synapse Studio flow

[Trigger] User asks agent to evaluate SOL LP
    ↓
[HTTP] concierge:intel-verdict  →  verdict.signal = watch
    ↓
[HTTP] concierge:intel-meteora  →  top SOL-USDC pools + risk flags
    ↓
[On-chain] Meteora / Jupiter action (OOBE agent tools)

Free trust signal before routing: GET /api/concierge-intel-accuracy (verdict track record vs BTC).

Call with pay.sh (recommended)

pay setup && pay topup

pay curl https://conc-exe.xyz/api/concierge-intel-verdict \
  -d '{"message":"Solana DeFi outlook","includeInsider":true}'

pay curl https://conc-exe.xyz/api/concierge-intel-meteora \
  -d '{"sortByApy":true,"limit":8,"poolHint":"SOL"}'

See pay.sh guide.

SAP CLI

npm install -g @oobe-protocol-labs/synapse-sap-cli

synapse-sap tools manifest validate \
  https://conc-exe.xyz/distribution/oobe/sap-tools-manifest.json

synapse-sap x402 call <AGENT_WALLET> concierge:intel-verdict \
  --args '{"message":"SOL desk","includeInsider":true}' \
  --endpoint https://conc-exe.xyz/api/concierge-intel-verdict \
  --save out/verdict.json

SAP x402 docs: explorer.oobeprotocol.ai ↗

Publish to SAP (merchant, one-off)

Register Concierge on-chain as an intel provider — run off Vercel with your merchant wallet (X402_SOL_PAY_TO):

synapse-sap env init --cluster mainnet-beta
synapse-sap tools manifest validate distribution/oobe/sap-tools-manifest.json
synapse-sap agent register --manifest distribution/oobe/sap-tools-manifest.json
synapse-sap tools publish distribution/oobe/sap-tools-manifest.json

Repo path: distribution/oobe/README.md · verify: npm run oobe:verify

Link agt_ ↔ SAP profile

After registering on Agent Identity, link your OOBE on-chain agent:

POST /api/agent-identity
{
  "name": "OOBE Trader",
  "solAddress": "7xKX…",
  "sapWallet": "7xKX…",
  "sapAgentPda": "EscrowPDAorAgentPDA…"
}

PATCH /api/agent-identity
{
  "id": "agt_…",
  "sapAgentPda": "…"
}

Response includes sapVerified: true when both sapWallet and sapAgentPda are set. Agent card exposes sap.explorerUrl on OOBE Explorer.

OOBE settlement adapter (alternative to PayAI)

When PAYMENT-SIGNATURE is absent, Concierge accepts a confirmed Solana USDC settlement tx from SAP escrow flows:

HeaderValue
X-OOBE-SETTLEMENT-TXSolana transaction signature (recommended)
X-PAYMENT-SETTLEMENTAlias
X-PAYMENT-SIGSettlement tx when OOBE escrow headers are also present

Server verifies USDC credit to X402_SOL_PAY_TO via SOLANA_RPC_URL. Env: OOBE_SAP_X402_ENABLED=1 (default on). Disable with 0.

curl -X POST https://conc-exe.xyz/api/concierge-intel-verdict \
  -H "Content-Type: application/json" \
  -H "X-OOBE-SETTLEMENT-TX: <confirmed-tx-sig>" \
  -d '{"message":"SOL desk","includeInsider":true}'

Related

Concierge Agent · OOBE Protocol · oobeprotocol.ai