Developers and partners

Build on the accountability layer.

oddly is a deterministic commerce engine, and it opens that engine to the systems built on top of commerce. Every response is traceable to the exact rule that produced it. The observed commerce corpus is a public data asset you can query with no account. And no path through oddly can increase spend without a human. Read it, verify a change before it is made, or put the guardrail in the path of a system that acts.

Read the API reference Talk to us

First call, no key: ask the observed commerce corpus what it covers.

Request

curl https://myoddly.com/api/public/mcp \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call",
       "params":{"name":"benchmark_categories","arguments":{}}}'

Response

{
  "jsonrpc": "2.0",
  "id": 1,
  "result": {
    "content": [{ "type": "text",
      "text": "oddly's corpus covers <N> categories,
               <M> observed listings in total. All
               figures are observed public storefront
               data. ..." }],
    "structuredContent": {
      "categories": [ ... ],
      "total_observations": <M>
    }
  }
}

Why build on oddly

Capability first.

Deterministic and traceable

Every response is traceable to the exact rule that produced it. Same inputs, same outputs, with no model in the hot path, so an answer is auditable, cacheable, and reproducible. It is the same accountability the platform headline is built on, exposed to you as a primitive.

The observed commerce corpus

Observed price and assortment benchmarks across categories, built from public storefront data. It is a data asset in its own right: list the covered categories and read their bands with no account, or read the same corpus through the Platform API.

Spend cannot rise without a human

No path through oddly can increase spend. Every change it can make is decrease-only, reversible, and recorded. That is a safety property of the whole platform, not a per-integration setting, so anything you build on top of it inherits it.

How to reach it

Three surfaces.

Platform API

Live

The v1 REST API over the deterministic primitives. Verify whether a proposed change would be blocked before it is made, read observed category benchmarks, and preview an action or a prescription through the dry-run ceiling. Bearer key, read-only, OpenAPI described.

API reference

Public MCP server

Live, no key

An unauthenticated MCP server over oddly's observed commerce corpus and the free storefront grader. Add it by URL in any MCP-capable agent or assistant, with no account. Three tools: list covered categories, look up observed price and assortment benchmarks, and audit a public storefront.

https://myoddly.com/api/public/mcp

Server descriptor Setup docs

Partner path

Open

For a tool that acts on a merchant's connected accounts, put oddly's deterministic guardrail in the path so every change is verified, decrease-only, reversible, and recorded. Acting on Meta or Google ad accounts is one such application; the same path fits any system that mutates commerce on a merchant's behalf. Talk to us about a partnership.

Become a partner The platform

Who builds on oddly

One capability, many applications.

Agent and orchestrator builders who need a deterministic check before anything is applied, and a response they can trace back to the rule that produced it.
Internal platform teams wiring approval-gated automation into an existing stack, who want a verifiable record of every change.
Risk and finance teams that need a spend constraint they can prove: a system structurally incapable of increasing spend without a human.
Partners and integrators building tools that act on a merchant's Meta or Google ad accounts, one application of the same guardrail.
Agent and assistant users who want observed commerce benchmarks and a free storefront audit, added by URL with no account.

The merchant who runs oddly on their own store is still the primary customer. The developer surface opens the same deterministic rules to the systems and partners that act on commerce on a merchant's behalf.

Want the full product story behind these primitives? See the platform overview, or read the API reference.

Running a Shopify store and looking for the merchant product?

Back to oddly for merchants