ModRetro

ModRetro Inc. designs and sells modern recreations of classic game consoles — the Chromatic, an FPGA-based Game Boy-compatible handheld, and the M64, a Nintendo 64-style console — along with physical cartridges, controllers and accessories. It is a consumer hardware company, not a software vendor, and it publishes no developer portal, no OpenAPI and no SDKs. It does, however, run a live agent-facing commerce API: its Shopify storefront at modretro.com serves a Universal Commerce Protocol (UCP 2026-04-08) merchant profile at /.well-known/ucp and a remote Model Context Protocol server at /api/ucp/mcp exposing 13 catalog, cart, checkout and order tools, advertised from its own robots.txt, /agents.md and /llms.txt, with idempotency required on checkout completion and an explicit human-approval rule on payment. Separately, ModRetro publishes the Chromatic's FPGA and MCU design files on GitHub under GPL-3.0 with a dated firmware changelog.

ModRetro publishes 1 API on the APIs.io network. Tagged areas include Company, Consumer Electronics, Gaming, Retro Gaming, and Hardware.

ModRetro’s developer surface includes documentation, authentication, changelog, support, engineering blog, pricing, signup flow, and 22 more developer resources.

🌐 Visit website 📡 Source on GitHub
29.9/100 thin ▬ flat Agent 25/100 agent aware saas Full breakdown ↓
scored 2026-09-01 · rubric v0.17.2
1 APIs 1 MCP Servers
CompanyConsumer ElectronicsGamingRetro GamingHardwareE-CommerceAgentic CommerceMCPUniversal Commerce ProtocolOpen Source Hardware

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-09-01 · rubric v0.17.2
Composite quality — 29.9/100 · thin
Contract Quality 0.0 / 25
Developer Ergonomics 6.1 / 20
Access Clarity 8.9 / 20
Operational Transparency 5.1 / 13
Contract Governance 2.2 / 12
Discoverability 7.6 / 10
Agent readiness — 25/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 9 / 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 0 / 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/modretro: 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 1

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

ModRetro Agent Commerce API (UCP over MCP)

ModRetro's agent-facing commerce API. A remote Model Context Protocol server implementing the Universal Commerce Protocol shopping service (versions 2026-04-08 and 2026-01-23), ...

MCP Servers 1

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

ModRetro MCP Server

MCP SERVER

Pricing Plans 1

Published pricing tiers and plan structures.

Modretro Plans Pricing

0 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Modretro Rate Limits

2 limits

RATE LIMITS

Security Posture 2

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

Modretro Authentication

openIdConnect/oauth2/http · 3 schemes

SECURITY

Modretro Domain Security

TLSv1.3 · HSTS · DNSSEC · DMARC

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

Modretro Scopes

4 scopes · authorizationCode

4 scopes

SCOPES

Resources

Get Started 1

Portal, sign-up, and the first successful call

SignUp
SignUp

Documentation 1

Reference material describing how the API behaves

Documentation
Documentation

Agent Surfaces 4

MCP servers, agent skills, and machine-readable catalogs

LLMsTxt
LLMsTxt
 MCPServer
MCPServer
 WellKnown
WellKnown
 AgentSkill
AgentSkill

Design & Contract 6

Pagination, idempotency, versioning, errors, and events

Conventions
Conventions
 Idempotency
Idempotency
 ErrorCatalog
ErrorCatalog
 Conformance
Conformance
 DataModel
DataModel
 Lifecycle
Lifecycle

Build 2

SDKs, sample code, and the tooling you integrate with

Packages
Packages
 GitHubOrganization
GitHubOrganization

Access & Security 3

Authentication, authorization, and security posture

DomainSecurity
DomainSecurity
 Authentication
Authentication
 OAuthScopes
OAuthScopes

Operate 5

Status, limits, changes, and where to get help

RateLimits
RateLimits
 ChangeLog
ChangeLog
 Support
Support
 HelpCenter
HelpCenter
 Community
Community

Commercial 4

Pricing, plans, and the legal terms of use

Plans
Plans
 Pricing
Pricing
 TermsOfService
TermsOfService
 PrivacyPolicy
PrivacyPolicy

Company 3

The organization behind the API

Website
Website
 Blog
Blog
 BlogRSS
BlogRSS

Source (apis.yml)

apis.yml Raw ↑ 
aid: modretro
name: ModRetro
description: 'ModRetro Inc. designs and sells modern recreations of classic game consoles — the Chromatic, an FPGA-based Game
  Boy-compatible handheld, and the M64, a Nintendo 64-style console — along with physical cartridges, controllers and accessories.
  It is a consumer hardware company, not a software vendor, and it publishes no developer portal, no OpenAPI and no SDKs.
  It does, however, run a live agent-facing commerce API: its Shopify storefront at modretro.com serves a Universal Commerce
  Protocol (UCP 2026-04-08) merchant profile at /.well-known/ucp and a remote Model Context Protocol server at /api/ucp/mcp
  exposing 13 catalog, cart, checkout and order tools, advertised from its own robots.txt, /agents.md and /llms.txt, with
  idempotency required on checkout completion and an explicit human-approval rule on payment. Separately, ModRetro publishes
  the Chromatic''s FPGA and MCU design files on GitHub under GPL-3.0 with a dated firmware changelog.'
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
image: https://modretro.com/cdn/shop/files/MR_SocialShare_ModRetro.png?v=1780328409&width=1200
url: https://raw.githubusercontent.com/api-evangelist/modretro/refs/heads/main/apis.yml
x-type: company
x-source: harvest:secondary-market
specificationVersion: '0.20'
created: '2026-08-26'
modified: '2026-08-26'
tags:
- Company
- Consumer Electronics
- Gaming
- Retro Gaming
- Hardware
- E-Commerce
- Agentic Commerce
- MCP
- Universal Commerce Protocol
- Open Source Hardware
tags_raw:
- Company
- Consumer Electronics
- Gaming
- Retro Gaming
- Hardware
- E-Commerce
- Agentic Commerce
- Model Context Protocol
- Universal Commerce Protocol
- Open Source Hardware
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
apis:
- name: ModRetro Agent Commerce API (UCP over MCP)
  description: ModRetro's agent-facing commerce API. A remote Model Context Protocol server implementing the Universal Commerce
    Protocol shopping service (versions 2026-04-08 and 2026-01-23), exposing 13 tools across catalog search and lookup, cart,
    checkout and order. initialize and tools/list answer anonymously; every tools/call requires a fetchable UCP agent-profile
    URI, and the order and checkout tools additionally require a Shopify agent JWT. complete_checkout requires an idempotency
    key and, per ModRetro's own robots.txt and /agents.md, explicit contemporaneous human approval of payment.
  humanURL: https://modretro.com/agents.md
  baseURL: https://modretro.com/api/ucp/mcp
  tags:
  - Agentic Commerce
  - MCP
  - Universal Commerce Protocol
  - E-Commerce
  - Catalog
  - Checkout
  tags_raw:
  - Agentic Commerce
  - Model Context Protocol
  - Universal Commerce Protocol
  - E-Commerce
  - Catalog
  - Checkout
  properties:
  - type: MCPServer
    url: mcp/modretro-mcp.yml
  - type: Documentation
    url: https://modretro.com/agents.md
  - type: Authentication
    url: authentication/modretro-authentication.yml
  - type: OAuthScopes
    url: scopes/modretro-scopes.yml
  - type: RateLimits
    url: rate-limits/modretro-rate-limits.yml
  - type: ErrorCatalog
    url: errors/modretro-problem-types.yml
  - type: DataModel
    url: data-model/modretro-data-model.yml
common:
- type: DomainSecurity
  url: security/modretro-domain-security.yml
- type: Website
  url: https://modretro.com/
- type: Documentation
  url: https://modretro.com/agents.md
- type: LLMsTxt
  url: llms/modretro-llms.txt
- type: MCPServer
  url: mcp/modretro-mcp.yml
- type: WellKnown
  url: well-known/modretro-well-known.yml
- type: Authentication
  url: authentication/modretro-authentication.yml
- type: OAuthScopes
  url: scopes/modretro-scopes.yml
- type: Conventions
  url: conventions/modretro-conventions.yml
- type: Idempotency
  url: conventions/modretro-conventions.yml
- type: RateLimits
  url: rate-limits/modretro-rate-limits.yml
- type: ErrorCatalog
  url: errors/modretro-problem-types.yml
- type: Conformance
  url: conformance/modretro-conformance.yml
- type: DataModel
  url: data-model/modretro-data-model.yml
- type: Lifecycle
  url: lifecycle/modretro-lifecycle.yml
- type: ChangeLog
  url: changelog/modretro-changelog.yml
- type: Packages
  url: packages/modretro-packages.yml
- type: Plans
  url: plans/modretro-plans-pricing.yml
- type: AgentSkill
  url: skills/_index.yml
- type: GitHubOrganization
  url: https://github.com/ModRetro
- type: Support
  url: https://support.modretro.com/
- type: HelpCenter
  url: https://support.modretro.com/
- type: Community
  url: https://forums.modretro.com/
- type: Blog
  url: https://modretro.com/blogs/blog
- type: BlogRSS
  url: https://modretro.com/blogs/blog.atom
- type: Pricing
  url: https://modretro.com/collections/all
- type: SignUp
  url: https://modretro.com/customer_authentication/redirect?locale=en&region_country=US
- type: TermsOfService
  url: https://modretro.com/policies/terms-of-service
- type: PrivacyPolicy
  url: https://modretro.com/policies/privacy-policy
x-enrichment:
  date: '2026-08-26'
  status: enriched
  artifacts_added: 24
  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/modretro"
All providers 
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose 
curl "https://apis.io/api/v1/providers/modretro/operations?limit=25"
How their score was established 
curl "https://apis.io/api/v1/providers/modretro/evidence"

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

Get an API key

Free tier, no email required.

GitHub Google LinkedIn

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