Omaze website screenshot

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 publishes 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 23 more developer resources.

29.0/100 thin ▬ flat Agent 30/100 agent ready Full breakdown ↓
scored 2026-08-25 · rubric v0.14.0
3 APIs 1 MCP Servers
CompanyCharityFundraisingNon-ProfitPrize DrawsSweepstakesE-CommerceAgentic CommerceUniversal Commerce ProtocolMCPShopifyUnited KingdomGermany

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-08-25 · rubric v0.14.0
Composite quality — 29.0/100 · thin
Contract Quality 0.0 / 25
Developer Ergonomics 10.4 / 20
Access Clarity 6.8 / 20
Operational Transparency 0.3 / 13
Contract Governance 2.2 / 12
Discoverability 9.3 / 10
Agent readiness — 30/100 · agent ready
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 Surface 5 / 5
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. This rating is computed from github.com/api-evangelist/omaze: open an issue to ask a question, or submit a pull request to add artifacts. Want it done for you? Prioritized profiling — $2,500 →

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

Rate Limits 1

Documented rate limits and quota policies.

Omaze Rate Limits

0 limits

RATE LIMITS

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

OAuth 2.0 · no documented scopes

0 scopes

SCOPES

Resources

Get Started 4

Portal, sign-up, and the first successful call

Documentation 1

Reference material describing how the API behaves

Agent Surfaces 4

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 4

Pagination, idempotency, versioning, errors, and events

Build 1

SDKs, sample code, and the tooling you integrate with

Access & Security 3

Authentication, authorization, and security posture

Operate 3

Status, limits, changes, and where to get help

Commercial 2

Pricing, plans, and the legal terms of use

Company 5

The organization behind the API

Other 2

Properties that don't map to a standard resource type

Source (apis.yml)

apis.yml Raw ↑
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
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
- 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
- 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
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/
x-enrichment:
  date: '2026-08-02'
  status: enriched
  artifacts_added: 21
  pass: local-v1

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"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no email required.

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