Omaze

Omaze is a for-profit social-impact entertainment company that runs online prize draws to raise money for charity. Founded in 2012 in Culver City, California by Matthew Pohlson and Ryan Cummins, it lets people enter draws for houses, supercars, cash and once-in-a-lifetime experiences, with a share of every entry going to a partner nonprofit; the company reports raising more than $250 million for over 600 charities and creating 50+ millionaires. Its live consumer operations today are the United Kingdom (omaze.co.uk) and Germany (omaze.de), both built on Shopify, while omaze.com serves as the corporate and brand site. Omaze publishes no developer program, no OpenAPI and no SDKs, but both storefronts do expose a genuine machine-readable agent surface: a Universal Commerce Protocol (UCP) merchant profile at /.well-known/ucp, a UCP Shopping MCP endpoint at /api/ucp/mcp, published agent instructions at /llms.txt and /agents.md, anonymous read-only storefront product JSON, and a standards-compliant OpenID Connect authorization server for customer accounts.

Omaze is listed with 3 APIs on the APIs.io network. Tagged areas include Company, Charity, Fundraising, Non-Profit, and Prize Draws.

Omaze’s developer surface includes documentation, getting-started guide, authentication, support, engineering blog, signup flow, and 28 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

31.7/100 thin ▬ flat Agent 24/100 agent aware Front door AI 1/6 silent saas Full breakdown ↓
scored 2026-11-13 · rubric v0.28.0 · Show this score on your site →

3 APIs 1 MCP Servers 1 Agent Skills

Company Charity Fundraising Non-ProfitPrize DrawsSweepstakes E-Commerce Agentic Commerce Universal Commerce Protocol MCP Shopify United Kingdom Germany

Kin Score

Kin Score How this is scored →
scored 2026-11-13 · rubric v0.28.0

Composite quality — 31.7/100 · thin

Contract Quality 0.0 / 21

Developer Ergonomics 8.8 / 17

Access Clarity 7.2 / 17

Operational Transparency 0.5 / 11

Contract Governance 1.9 / 10

Discoverability 6.8 / 9

Regulatory Posture 4.3 / 15

Agent readiness — 24/100 · agent aware

Machine-Readable Contract 0 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

MCP Server 12 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 7 / 7

Typed Event Surface 0 / 6

Agent Skills 5 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 6 / 6

Protected Resource Metadata 5 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 5 / 5

Pagination 5 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

Regulatory Posture applies to this provider. Its tags matched the Horizontal (data, software, accessibility, platform) regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.

The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/omaze/"><img src="https://apis.io/badge/omaze/card.svg" alt="Omaze on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

Machine-Readable Contract +18 pts — api_specs includes an OpenAPI document Ask about this →
Agentic Access Contract +10 pts — agentic_access artifact present (x-agentic-access), graded by author Ask about this →
Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented) Ask about this →
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0 Ask about this →
Request/Response Examples +7 pts — share of operations carrying request/response examples; else an Examples / Code Samples link Ask about this →
Registration Without a Human +6 pts — a `registration_endpoint` in the served RFC 8414 / OIDC discovery document Ask about this →

5 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Contract Quality scores 0.0 — up to +25.0 composite points Ask about this →
Operational Transparency scores 4.8 — up to +12.4 composite points Ask about this →
Access Clarity scores 42.6 — up to +11.5 composite points Ask about this →

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

Not sure how this applies to your stack? Ask about any one item. Kin Lane reads every question, looks at your profile and your situation, and replies with what a fix would take — scoped to that one area, priced up front, yours whether you ship it or not. Ask a question →

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/omaze/apis.yml: open an issue on github.com/api-evangelist/omaze to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Standards implemented 3

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

Model Context Protocol (MCP)

measured — observed by APIs.io (platform)

Universal Commerce Protocol (UCP)

tagged — the provider's own APIs.json carries the standard as a tag; implementation not verified

OAuth 2.0 Protected Resource Metadata

measured — observed by APIs.io (verified)

APIs 3

Individual APIs this provider publishes, each with its own machine-readable definition.

Omaze UK UCP Shopping MCP

The Universal Commerce Protocol Shopping service that Omaze UK exposes over the Model Context Protocol, advertised by Omaze in its own /agents.md and /llms.txt and described by ...

Omaze Germany UCP Shopping MCP

The German-market counterpart of the Omaze UCP Shopping service, exposed over MCP at omaze.de/api/ucp/mcp and described by the merchant profile at omaze.de/.well-known/ucp. Same...

Omaze UK Storefront JSON

The anonymous, read-only JSON surface of the Omaze UK storefront, documented by Omaze itself in /agents.md for agents that only need to read store data without transacting. Cove...

MCP Servers 1

Model Context Protocol servers that expose these APIs to AI agents.

Omaze MCP Server

Omaze does not operate a general-purpose developer MCP server. What it does operate — on both of its live storefronts — is a Universal Commerce Protocol (UCP) Shopping service e...

MCP SERVER

Agent Skills 1

Packaged agent skills for driving this provider's APIs from an AI assistant.

omaze-uk-enter-prize-draw

AGENT SKILL

Rate Limits 1

Documented rate limits and quota policies.

Omaze Rate Limits

0 limits

RATE LIMITS

Terms of Service 1

What its API terms permit and prohibit, quoted from its own page.

Omaze

9 quoted statements, read from Omaze's own page on 2026-11-10.

TERMS

Privacy & Data 1

Its role, the data it processes, retention and transfers, quoted from its own privacy page.

Omaze

27 quoted statements, read from Omaze's own page on 2026-11-10.

PRIVACY

Eligibility 1

Who may sign up and where, quoted from its own terms.

Omaze

4 quoted statements, read from Omaze's own page on 2026-11-10.

ELIGIBILITY

AI Preferences 1

Its stance on AI training, inference and agents, quoted from its own pages.

Omaze

1 quoted statement, read from Omaze's own page on 2026-11-10.

AI PREFS

Data License 1

How its data and outputs may be reused, quoted from its own terms.

Omaze

1 quoted statement, read from Omaze's own page on 2026-11-10.

LICENSE

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Omaze Authentication

2 schemes

SECURITY

Omaze Domain Security

TLSv1.3 · HSTS · DNSSEC · DMARC

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

Omaze Scopes

4 scopes · authorization_code

4 scopes

SCOPES

Resources

Get Started 4

Portal, sign-up, and the first successful call

DeveloperPortal

DeveloperPortal

GettingStarted

GettingStarted

SignUp

SignUp

Login

Documentation 2

Reference material describing how the API behaves

Documentation

Documentation

AIPreferences

AIPreferences

Agent Surfaces 4

MCP servers, agent skills, and machine-readable catalogs

LLMsTxt

MCPServer

WellKnown

AgentSkill

Design & Contract 4

Pagination, idempotency, versioning, errors, and events

Conventions

ErrorCatalog

Lifecycle

Conformance

Build 1

SDKs, sample code, and the tooling you integrate with

GitHubOrganization

GitHubOrganization

Access & Security 3

Authentication, authorization, and security posture

DomainSecurity

DomainSecurity

Authentication

Authentication

OAuthScopes

OAuthScopes

Operate 3

Status, limits, changes, and where to get help

RateLimits

RateLimits

Support

Support

HelpCenter

HelpCenter

Commercial 4

Pricing, plans, and the legal terms of use

TermsOfService

PrivacyPolicy

UsageTerms

DataLicense

Company 5

The organization behind the API

Website

Website

Website

Blog

Careers

Other 4

Properties that don't map to a standard resource type

OpenIDConnect

OpenIDConnect

SecondaryMarketListing

SecondaryMarketListing

DataProcessing

DataProcessing

Eligibility

Eligibility

Source (apis.yml)

aid: omaze
name: Omaze
description: 'Omaze is a for-profit social-impact entertainment company that runs online prize draws to raise money for charity.
  Founded in 2012 in Culver City, California by Matthew Pohlson and Ryan Cummins, it lets people enter draws for houses, supercars,
  cash and once-in-a-lifetime experiences, with a share of every entry going to a partner nonprofit; the company reports raising
  more than $250 million for over 600 charities and creating 50+ millionaires. Its live consumer operations today are the
  United Kingdom (omaze.co.uk) and Germany (omaze.de), both built on Shopify, while omaze.com serves as the corporate and
  brand site. Omaze publishes no developer program, no OpenAPI and no SDKs, but both storefronts do expose a genuine machine-readable
  agent surface: a Universal Commerce Protocol (UCP) merchant profile at /.well-known/ucp, a UCP Shopping MCP endpoint at
  /api/ucp/mcp, published agent instructions at /llms.txt and /agents.md, anonymous read-only storefront product JSON, and
  a standards-compliant OpenID Connect authorization server for customer accounts.'
url: https://raw.githubusercontent.com/api-evangelist/omaze/refs/heads/main/apis.yml
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: false
  label: Hosted service · you call their endpoint
  confidence: medium
  source:
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source:
  - authentication
  - scopes
  - rate-limits
  - security
  generated: '2026-11-13'
  method: derived
image: https://omaze.co.uk/cdn/shop/files/social_image-2.png?v=1753698911
x-type: company
x-source: harvest:secondary-market
x-tier: profiled
x-tier-reason: enrichment
specificationVersion: '0.23'
created: '2026-08-02'
modified: '2026-08-02'
tags:
- Company
- Charity
- Fundraising
- Non-Profit
- Prize Draws
- Sweepstakes
- E-Commerce
- Agentic Commerce
- Universal Commerce Protocol
- MCP
- Shopify
- United Kingdom
- Germany
tags_raw:
- Company
- Charity
- Fundraising
- Nonprofit
- Prize Draws
- Sweepstakes
- Ecommerce
- Agentic Commerce
- Universal Commerce Protocol
- Model Context Protocol
- Shopify
- United Kingdom
- Germany
apis:
- aid: omaze:omaze-uk-ucp-shopping-mcp
  name: Omaze UK UCP Shopping MCP
  description: The Universal Commerce Protocol Shopping service that Omaze UK exposes over the Model Context Protocol, advertised
    by Omaze in its own /agents.md and /llms.txt and described by the merchant profile at /.well-known/ucp. It lets an agent
    search the Omaze UK prize-draw catalog, build a cart, and drive a checkout up to the point of buyer-approved payment.
    Protocol version 2026-04-08 (2026-01-23 also accepted). The endpoint is live but will not negotiate a session until the
    calling agent presents a resolvable UCP agent profile URI, so per-tool input schemas require a profile-bearing introspection
    run.
  humanURL: https://omaze.co.uk/agents.md
  baseURL: https://omaze.co.uk/api/ucp/mcp
  tags:
  - MCP
  - Agentic Commerce
  - Universal Commerce Protocol
  - E-Commerce
  - Checkout
  tags_raw:
  - MCP
  - Agentic Commerce
  - Universal Commerce Protocol
  - Ecommerce
  - Checkout
  properties:
  - type: MCPServer
    url: mcp/omaze-mcp.yml
  - type: WellKnown
    url: well-known/omaze-uk-ucp.json
  - type: Authentication
    url: authentication/omaze-authentication.yml
  - type: RateLimits
    url: rate-limits/omaze-rate-limits.yml
  - type: ErrorCatalog
    url: errors/omaze-problem-types.yml
  x-surface: platform-generated
  x-platform: shopify
  x-platform-surface: ucp
- aid: omaze:omaze-de-ucp-shopping-mcp
  name: Omaze Germany UCP Shopping MCP
  description: The German-market counterpart of the Omaze UCP Shopping service, exposed over MCP at omaze.de/api/ucp/mcp and
    described by the merchant profile at omaze.de/.well-known/ucp. Same protocol version (2026-04-08) and same shopping capabilities
    as the UK store; the payment-handler set differs (Google Pay and Shopify card, without Shop Pay). Backed by its own Shopify
    Customer Accounts issuer at accounts.omaze.de.
  humanURL: https://omaze.de/agents.md
  baseURL: https://omaze.de/api/ucp/mcp
  tags:
  - MCP
  - Agentic Commerce
  - Universal Commerce Protocol
  - E-Commerce
  - Germany
  tags_raw:
  - MCP
  - Agentic Commerce
  - Universal Commerce Protocol
  - Ecommerce
  - Germany
  properties:
  - type: MCPServer
    url: mcp/omaze-mcp.yml
  - type: WellKnown
    url: well-known/omaze-de-ucp.json
  x-surface: platform-generated
  x-platform: shopify
  x-platform-surface: ucp
- aid: omaze:omaze-uk-storefront-json
  name: Omaze UK Storefront JSON
  description: The anonymous, read-only JSON surface of the Omaze UK storefront, documented by Omaze itself in /agents.md
    for agents that only need to read store data without transacting. Covers product listings (/products.json), individual
    products (/products/{handle}.json), collection contents (/collections/{handle}/products.json) and the sitemap. No credentials
    are required and no rate limit is published for it; Omaze publishes no OpenAPI describing it.
  humanURL: https://omaze.co.uk/agents.md
  baseURL: https://omaze.co.uk
  tags:
  - Product
  - Catalog
  - E-Commerce
  - Read Only
  tags_raw:
  - Products
  - Catalog
  - Ecommerce
  - Read Only
  properties:
  - type: LLMsTxt
    url: llms/omaze-llms.txt
  - type: Conventions
    url: conventions/omaze-conventions.yml
  x-surface: platform-generated
  x-platform: shopify
  x-platform-surface: storefront-json
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: DomainSecurity
  url: security/omaze-domain-security.yml
- type: Website
  url: https://www.omaze.com
- type: Website
  url: https://omaze.co.uk
- type: Website
  url: https://omaze.de
- type: DeveloperPortal
  url: https://omaze.co.uk/agents.md
- type: Documentation
  url: https://omaze.co.uk/agents.md
- type: GettingStarted
  url: https://omaze.co.uk/llms.txt
- type: LLMsTxt
  url: llms/omaze-llms.txt
- type: MCPServer
  url: mcp/omaze-mcp.yml
- type: WellKnown
  url: well-known/omaze-well-known.yml
- type: Authentication
  url: authentication/omaze-authentication.yml
- type: OAuthScopes
  url: scopes/omaze-scopes.yml
- type: OpenIDConnect
  url: https://omaze.co.uk/.well-known/openid-configuration
- type: Conventions
  url: conventions/omaze-conventions.yml
- type: RateLimits
  url: rate-limits/omaze-rate-limits.yml
- type: ErrorCatalog
  url: errors/omaze-problem-types.yml
- type: Lifecycle
  url: lifecycle/omaze-lifecycle.yml
- type: Conformance
  url: conformance/omaze-conformance.yml
- type: AgentSkill
  url: skills/_index.yml
- type: Support
  url: https://omaze.co.uk/pages/contact-us
- type: HelpCenter
  url: https://omaze.co.uk/pages/faqs
- type: Blog
  url: https://omaze.co.uk/blogs/news
- type: GitHubOrganization
  url: https://github.com/Omaze
- type: SignUp
  url: https://omaze.co.uk/account/register
- type: Login
  url: https://omaze.co.uk/account/login
- type: TermsOfService
  url: https://omaze.co.uk/pages/legal-terms
- type: PrivacyPolicy
  url: https://omaze.co.uk/policies/privacy-policy
- type: Careers
  url: https://omaze.company/careers.html
- type: SecondaryMarketListing
  url: https://forgeglobal.com/omaze_stock/
- type: UsageTerms
  url: terms/omaze-terms-of-service.yml
- type: DataProcessing
  url: privacy/omaze-privacy-policy.yml
- type: Eligibility
  url: eligibility/omaze-eligibility.yml
- type: AIPreferences
  url: ai-preferences/omaze-ai-preferences.yml
- type: DataLicense
  url: data-license/omaze-data-license.yml
x-enrichment:
  date: '2026-08-02'
  status: enriched
  artifacts_added: 21
  pass: local-v1

Omaze API — frequently asked questions

Does Omaze have an API?

Yes. APIs.io lists 3 APIs from Omaze, including Omaze UK UCP Shopping MCP, Omaze Germany UCP Shopping MCP and Omaze UK Storefront JSON.

How do I authenticate with the Omaze API?

Omaze documents its authentication (2 schemes). The details are profiled on APIs.io as Omaze Authentication.

Does Omaze have an MCP server?

Yes. APIs.io lists 1 MCP server for Omaze: Omaze does not operate a general-purpose developer MCP server. What it does operate — on both of its live storefronts — is a Universal Commerce Protocol (UCP) Shopping service exposed over MCP, provis

Is the Omaze API ready for AI agents?

Omaze has a Kin Score of 31.7 out of 100 (thin) and an Agent Readiness score of 23.7 (agent-aware), scored by API Evangelist on 2026-11-13.

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/omaze"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/omaze/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/omaze/evidence"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.