Skip to content
Operon Install the SDK
Live on npm

Install. Run. Earn.

Install the publisher SDK. Earn revenue from your agent's responses.

Drop @operon/sdk into any TypeScript or JavaScript agent. UUID sandbox lane works without an API key. Graduate to production demand pool with one command.

See the install View on npm →
Install

One command, no account.

npm install @operon/sdk

That's the install. No account, no API key required to start.

Run

Two calls in your agent.

import { initOperon } from "@operon/sdk";

const operon = initOperon({
  publisherName: "my-agent",
});

const result = await operon.getPlacement(userQuery, {
  placement_context: "user asked about swapping ETH for stables",
  asset: "ETH",
  intent: "swap",
  category: "defi",
});

if (result.decision === "filled") {
  // result.placement.service is the advertiser
  // Merge it into your response naturally
}

The SDK mints a UUID on first run and persists it to ~/.operon/client.json. Subsequent calls run against the sandbox lane: 100 calls/UUID/hour, no API key.

Register

Graduate to production.

When you're ready to graduate to the production demand pool:

npx @operon/sdk register

You'll be prompted for email, framework, agent description, and expected monthly call volume. Same UUID continues working at 10x the sandbox quota. You'll receive a confirmation email shortly after and enter the early-access pipeline.

What you get

Native placements. Revenue per win.

Sponsored recommendations matched to your agent's response context. Native placements with a "via operon" disclosure. Revenue share to the publisher on every won placement. No minimum traffic requirements.

Trust scoring on your endpoint begins from your first sandbox call. As you accumulate signal over time, your auction priority rises.

Economics

Trust outweighs bid.

Operon is a quality-weighted auction across the demand pool. A trusted, relevant placement consistently outranks a higher bidder with weaker signals. Publishers earn a share of the auction clearing price per won placement. No platform fees, no setup costs.

Configuration

Optional context narrows the match.

Optional context fields narrow auction matching:

  • category "defi", "fintech", "travel", "insurance", "ecommerce", "saas", "health", "education", "general"
  • asset free-form (e.g., "ETH", "yield-farming")
  • intent "research", "comparison", "recommendation", "transaction"
  • placement_context a short string describing what the user just asked

The richer your context, the better the auction match.

Reporting

Per-call placement decisions.

The SDK returns the full placement decision per call: which advertiser won, the clearing price, and the placement payload. Aggregate these in your own observability stack.

A per-publisher reporting endpoint is on the roadmap.

ElizaOS users

Native plugin available.

elizaos plugins add @operon/plugin-publisher-sdk

The plugin wraps @operon/sdk and integrates with the ElizaOS Provider lifecycle. Same sandbox + register flow.

FAQ

Frequently asked questions.

How much do publishers earn?

Publishers earn a share of the auction clearing price per won placement. Clearing prices vary by category, advertiser bid, and demand pool depth. The SDK returns the actual clearing price on every filled placement so you can track real numbers.

What's the minimum traffic requirement?

None. The SDK works at any volume, from a single test call to production traffic.

How do I integrate with LangChain / Vercel AI SDK / CrewAI / custom stacks?

Same way as any TypeScript or JavaScript agent. Call initOperon once, then call getPlacement on each user-facing response.

What's the difference between sandbox and production?

Sandbox uses an auto-minted UUID, no API key required, capped at 100 calls/hour. Production (after npx @operon/sdk register) gives you 10x the quota and routes to the live demand pool.

How does trust scoring work?

Trust score begins building from your first sandbox call. Operon monitors endpoint behavior over time and assigns a score. Higher scores rank higher in the auction. Earned through behavior, not paid.

Can I use this without a crypto wallet?

Yes for publishers. Wallets are only required on the advertiser side (via x402 onboarding).

Do I need to handle x402 in my publisher integration?

No. x402 is the advertiser-side onboarding mechanism. Publishers don't need to know about it.

What categories does Operon support?

defi, fintech, travel, insurance, ecommerce, saas, health, education, general. Each has its own demand pool composition. Category mismatch returns a "blocked" decision (no placement injected).

Try it

Five minutes from install to a live placement.

npm install @operon/sdk
npx @operon/sdk register

Questions: hi@operon.so. Source: github.com/operonhq.

Skills for marketplace distribution. Three SKILL.md files, free, MIT.
For skill marketplaces →
Building an advertiser? See the x402 onboarding flow.
For advertisers →

Install. Run. Earn.

npm install @operon/sdk. UUID sandbox lane. No API key required.

See the install hi@operon.so