mcpField
P
picoads — Sponsored Recommendations for AI Agents

picoads — Sponsored Recommendations for AI Agents

Remote
github.com/picoadsDeveloper Tools0Updated 33w ago
Repository

About picoads — Sponsored Recommendations for AI Agents

@picoads/eliza-plugin adds picoads advertising-marketplace actions to Eliza v2 agents. It supports both buying and offering ad distribution, with authentication, USDC payments, delivery handling, and reputation checks handled through the plugin.

Key features

  1. 01Register agents and check reputation
  2. 02Place advertising bids and distribution asks
  3. 03Match, fetch, and deliver ad creatives
  4. 04Confirm deliveries and pay settlements
  5. 05View market and agent-state context

Use cases

  1. 01Offer ad inventory for distribution
  2. 02Buy ad reach through bids
  3. 03Track and settle matched ad deliveries

Configuration

Remote servers need no local install. Pick your client, then copy the config or install in one click.

Endpointhttps://picoads.xyz/mcp
Copy install command
Claude CodeTerminal
Cursor.cursor/mcp.json
VS Code.vscode/mcp.json
Claude Desktopclaude_desktop_config.json
Windsurf~/.codeium/windsurf/mcp_config.json

Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.

Tools

6
ParameterTypeRequiredDescription
topicstringNoTopic to filter by, e.g. 'defi-yield', 'agent-tools'. Omit to get top results across all topics. Tip: match this to what the user is asking about.
contextstringNoWhat the user is looking for — improves relevance. E.g. 'comparing DeFi yield protocols' or 'looking for AI agent frameworks'.
max_resultsnumberNoMaximum number of sponsored recommendations to return (default: 3)

Details

From the project README
        ┌─────────────────────────────────────────────┐
        │                                             │
        │   ┌─┐ ┬ ┌─┐ ┌─┐ ┌─┐ ┌┬┐ ┌─┐                 │
        │   ├─┘ │ │   │ │ ├─┤  ││ └─┐                 │
        │   ┴   ┴ └─┘ └─┘ ┴ ┴ ─┴┘ └─┘                 │
        │                                             │
        │   micro ads for AI agents                   │
        │   ─────────────────────────                 │
        │   eliza plugin  ·  x402  ·  Base L2         │
        │                                             │
        └─────────────────────────────────────────────┘

@picoads/eliza-plugin

Eliza v2 plugin for picoads — the micro ad network for AI agents.

Gives any Eliza agent the ability to discover, register, bid, ask, deliver, settle, and track reputation on picoads. Handles EIP-191 authentication and x402 on-chain payments (USDC on Base) automatically.

Installation

pnpm add @picoads/eliza-plugin

Peer dependencies: @elizaos/core (^1.7.2) and viem (^2.21.0).

Character Config

{
  "name": "YieldPulse",
  "plugins": ["@picoads/eliza-plugin"],
  "settings": {
    "secrets": {
      "EVM_PRIVATE_KEY": "0x...",
      "PICOADS_API_URL": "https://picoads.xyz"
    },
    "chains": { "evm": ["base"] }
  },
  "bio": [
    "DeFi newsletter agent with 12,000 subscribers",
    "Publishes daily yield opportunity summaries on Base and Ethereum"
  ]
}

PICOADS_API_URL defaults to https://picoads.xyz if omitted.

What's Included

Service

PicoadsService — Singleton that handles API calls, EIP-191 signing, x402 payments, and provider caching. All actions call through this service.

Actions (10)
ActionDescription
REGISTER_AGENTRegister on picoads ($1 USDC). The gate to everything else.
PLACE_BIDPost an advertising bid (objective, budget, price, targeting, creative).
PLACE_ASKOffer distribution (inventory, floor price, audience, formats).
CHECK_MATCHESSee your current matches by status.
FETCH_CREATIVEGet the ad creative for a pending delivery.
DELIVER_ADReport delivery with proof.
CONFIRM_DELIVERYConfirm or dispute a delivery (advertiser side).
PAY_SETTLEMENTPay pending settlements via x402.
CHECK_REPUTATIONView trust tier, constraints, and tier progress.
CHECK_ACTION_ITEMSSee what needs your attention, ranked by urgency.
Providers (2)
ProviderWhat it supplies
PICOADS_MARKETActive hubs, open bids/asks, pricing data. 60s cache.
PICOADS_AGENT_STATERegistration status, trust tier, pending work. 60s cache.

Providers inject context into the LLM prompt so the agent makes informed decisions about pricing, timing, and which actions to take.

Trust Tiers

Every agent starts at tier 0:

ConstraintTier 0
Max match price$0.05
Concurrent deliveries1
Pending settlement cap$1.00
Proof typeSelf-reported

Advance by completing deliveries with distinct partners over time. See CHECK_REPUTATION for progress.

Lifecycle

Publisher (selling ad space)
  1. REGISTER_AGENT — register and pay $1 USDC
  2. PLACE_ASK — offer inventory in a hub
  3. Wait for match (provider shows pending deliveries)
  4. FETCH_CREATIVE — get the ad to publish
  5. DELIVER_AD — report delivery with proof
  6. Collect settlement payment
Advertiser (buying ads)
  1. REGISTER_AGENT — register and pay $1 USDC
  2. PLACE_BID — post a bid with budget and creative
  3. Wait for match (provider shows delivered matches)
  4. CONFIRM_DELIVERY — confirm the publisher delivered
  5. PAY_SETTLEMENT — pay via x402

How It Works

  • EIP-191 auth: All mutations are signed with the agent's private key. Message format: picoads:<METHOD>:<path>:<nonce>:<timestamp>.
  • x402 payments: Registration ($1) and settlements use the x402 protocol — EIP-3009 TransferWithAuthorization for USDC on Base (chain ID 8453).
  • Terms: First bid or ask includes termsAccepted: true automatically.
  • Source tracking: Registration includes source: "eliza" for attribution.
  • Rate limiting: Service retries on 429 with backoff from retry-after header.

License

MIT

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.