AMI Paris

AMI Paris is a French contemporary ready-to-wear fashion house founded in 2011 by Alexandre Mattiussi and headquartered in Paris, known for its "Ami de coeur" heart logo. It sells menswear, womenswear, and accessories direct-to-consumer through amiparis.com, an online store built on Shopify. The store exposes a real agent-commerce surface: a Universal Commerce Protocol (UCP, ucp.dev) MCP endpoint advertised in /.well-known/ucp, a published /llms.txt and /agents.md with agent instructions, Shopify Customer Account OIDC/OAuth2 authentication, and read-only product/collection JSON endpoints. It was surfaced as a portfolio company of HongShan (Sequoia China) and profiled by the API Evangelist enrichment pipeline.

AMI Paris is listed with 1 API on the APIs.io network. Tagged areas include Company, Consumer, Fashion, Retail, and E-Commerce.

AMI Paris’ developer surface includes engineering blog, support, authentication, and 10 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

16.9/100 emerging ▬ flat Agent 17/100 agent aware Front door AI 1/6 silent Heartbeat 100/100 alive saas Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

1 API 1 MCP Servers

Company Consumer Fashion Retail E-Commerce Shopify Agentic Commerce Universal Commerce Protocol

Kin Score

Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0

Composite quality — 16.9/100 · emerging

Contract Quality 0.0 / 21

Developer Ergonomics 4.5 / 17

Access Clarity 2.9 / 17

Operational Transparency 0.0 / 11

Contract Governance 0.0 / 10

Discoverability 5.7 / 9

Regulatory Posture 3.8 / 15

Agent readiness — 17/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 0 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 0 / 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 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/ami-paris/"><img src="https://apis.io/badge/ami-paris/card.svg" alt="AMI Paris 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
Agentic Access Contract +10 pts — agentic_access artifact present (x-agentic-access), graded by author
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)
Stable Error Semantics +8 pts — OpenAPI $refs a shared error schema across 4xx/5xx responses (verified), else common[].type includes ErrorCatalog / ErrorCodes / DeclineCodes
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Rate-Limit Signaling +7 pts — OpenAPI responses document X-RateLimit-* / RateLimit headers (verified), else a rate_limits artifact or RateLimits link (documented)

8 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
Access Clarity scores 17.1 — up to +16.6 composite points
Developer Ergonomics scores 26.2 — up to +14.8 composite points

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.

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/ami-paris/apis.yml: open an issue on github.com/api-evangelist/ami-paris 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 →

Markets this provider is in provisional

The Kin Score Market layer reads a provider inside its market: its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted: not part of the Kin Score or agent readiness.

Market	Position	Depth	Registered MCP server	Declares compatibility
Fashion & Apparel (apparel, footwear, textiles)	undeclared	-	-	-

Registered MCP server and declares compatibility are report only — not weighted. Undeclared means we found nothing we can read, so there is no number: we never infer integrations.

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.

Universal Commerce Protocol (UCP)

measured — observed by APIs.io (shopify)

Model Context Protocol (MCP)

measured — observed by APIs.io (platform)

Agent Skills

measured — observed by APIs.io (published)

APIs 1

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

AMI Paris Agent Commerce (UCP)

Agent-facing commerce surface for the AMI Paris Shopify storefront — a Universal Commerce Protocol (UCP) MCP endpoint for catalog search, cart, checkout, fulfillment, discount, ...

MCP Servers 1

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

AMI Paris MCP Server

Remote MCP server at amiparis-prod.myshopify.com over HTTP; 5 tools listed.

MCP SERVER

Security Posture 2

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

Ami Paris Authentication

oauth2/openIdConnect · 1 scheme

SECURITY

Ami Paris Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

Ami Paris Scopes

4 scopes · authorizationCode

4 scopes

SCOPES

Resources

Get Started 1

Portal, sign-up, and the first successful call

Login

Agent Surfaces 4

MCP servers, agent skills, and machine-readable catalogs

MCPServer

LLMsTxt

AgentSkill

WellKnown

Access & Security 3

Authentication, authorization, and security posture

Authentication

Authentication

OAuthScopes

OAuthScopes

DomainSecurity

DomainSecurity

Operate 1

Status, limits, changes, and where to get help

Support

Support

Commercial 1

Pricing, plans, and the legal terms of use

PrivacyPolicy

PrivacyPolicy

Company 3

The organization behind the API

Blog

Blog

BlogRSS

BlogRSS

Website

Website

Source (apis.yml)

aid: ami-paris
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
  - security
  generated: '2026-11-06'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/ami-paris.png
name: AMI Paris
description: 'AMI Paris is a French contemporary ready-to-wear fashion house founded in 2011 by Alexandre Mattiussi and headquartered
  in Paris, known for its "Ami de coeur" heart logo. It sells menswear, womenswear, and accessories direct-to-consumer through
  amiparis.com, an online store built on Shopify. The store exposes a real agent-commerce surface: a Universal Commerce Protocol
  (UCP, ucp.dev) MCP endpoint advertised in /.well-known/ucp, a published /llms.txt and /agents.md with agent instructions,
  Shopify Customer Account OIDC/OAuth2 authentication, and read-only product/collection JSON endpoints. It was surfaced as
  a portfolio company of HongShan (Sequoia China) and profiled by the API Evangelist enrichment pipeline.'
url: https://raw.githubusercontent.com/api-evangelist/ami-paris/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- hongshan
x-tier: stub
x-tier-reason: portfolio-lead
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-10-06'
tags:
- Company
- Consumer
- Fashion
- Retail
- E-Commerce
- Shopify
- Agentic Commerce
- Universal Commerce Protocol
tags_raw:
- Company
- Consumer
- Fashion
- Retail
- Ecommerce
- Shopify
- Agent Commerce
- UCP
apis:
- name: AMI Paris Agent Commerce (UCP)
  description: Agent-facing commerce surface for the AMI Paris Shopify storefront — a Universal Commerce Protocol (UCP) MCP
    endpoint for catalog search, cart, checkout, fulfillment, discount, and order operations, plus unauthenticated storefront
    product/collection JSON browsing. Checkout requires explicit buyer approval.
  humanURL: https://www.amiparis.com/llms.txt
  tags:
  - Agentic Commerce
  - Universal Commerce Protocol
  - MCP
  - E-Commerce
  tags_raw:
  - Agent Commerce
  - UCP
  - MCP
  - Ecommerce
  properties:
  - type: MCPServer
    url: mcp/ami-paris-mcp.yml
  - type: LLMsTxt
    url: llms/ami-paris-llms.txt
  - type: Authentication
    url: authentication/ami-paris-authentication.yml
  - type: OAuthScopes
    url: scopes/ami-paris-scopes.yml
  x-surface: platform-generated
  x-platform: shopify
  x-platform-surface: ucp
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- url: https://www.amiparis.com/collections/unisex-new-arrivals
  type: Blog
- url: https://www.amiparis.com/collections/unisex-new-arrivals.atom
  type: BlogRSS
- type: Website
  url: https://amiparis.com
- type: Login
  url: https://www.amiparis.com/account/login
- type: Support
  url: https://www.amiparis.com/pages/contact-us
- type: PrivacyPolicy
  url: https://www.amiparis.com/policies/privacy-policy
- type: MCPServer
  url: mcp/ami-paris-mcp.yml
- type: LLMsTxt
  url: llms/ami-paris-llms.txt
- type: AgentSkill
  url: skills/_index.yml
- type: WellKnown
  url: well-known/ami-paris-well-known.yml
- type: Authentication
  url: authentication/ami-paris-authentication.yml
- type: OAuthScopes
  url: scopes/ami-paris-scopes.yml
- type: DomainSecurity
  url: security/ami-paris-domain-security.yml
x-enrichment:
  date: '2026-07-19'
  status: backfilled
  pass: local-v1
  note: backfilled from .gitignore signal + verified work evidence

AMI Paris API — frequently asked questions

Does AMI Paris have an API?

Yes. APIs.io lists 1 API from AMI Paris, including AMI Paris Agent Commerce (UCP).

How do I authenticate with the AMI Paris API?

AMI Paris documents its authentication (oauth2/openIdConnect · 1 scheme). The details are profiled on APIs.io as Ami Paris Authentication.

Does AMI Paris have an MCP server?

Yes. APIs.io lists 1 MCP server for AMI Paris: Remote MCP server at amiparis-prod.myshopify.com over HTTP; 5 tools listed.

Is the AMI Paris API ready for AI agents?

AMI Paris has a Kin Score of 16.9 out of 100 (emerging) and an Agent Readiness score of 17.4 (agent-aware), scored by API Evangelist on 2026-11-06.

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/ami-paris"

All providers

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

Every operation they expose

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

How their score was established

curl "https://apis.io/api/v1/providers/ami-paris/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.