Footway

Footway is a Nordic, data-driven e-commerce group (Nasdaq First North Growth Market, Stockholm) that operates the Footway footwear-and-fashion marketplace across roughly 24 European markets, carrying around 800 brands for more than two million customers, alongside its Operations-as-a-Service ("ECOM IN A BOX") merchant infrastructure at footwayplus.com / oaas.footway.com and a merchant portal at merchant.footwayplus.com. The consumer storefront at footway.com runs on Shopify and exposes an agent-native commerce surface: an llms.txt / agents.md agent guide, a Universal Commerce Protocol (UCP) merchant profile at /.well-known/ucp, a UCP MCP endpoint for buyer-approved agent checkout, and Shopify Customer Account OpenID Connect / OAuth 2.0 authentication.

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

Footway’s developer surface includes engineering blog, documentation, authentication, support, signup flow, and 13 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

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

1 API 1 MCP Servers 1 Agent Skills

Company Consumer E-Commerce Marketplace Retail Footwear Fashion Shopify Agentic Commerce Universal Commerce Protocol MCP Nordic

Kin Score

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

Composite quality — 27.4/100 · thin

Contract Quality 0.0 / 21

Developer Ergonomics 6.8 / 17

Access Clarity 5.8 / 17

Operational Transparency 0.0 / 11

Contract Governance 1.9 / 10

Discoverability 6.4 / 9

Regulatory Posture 5.1 / 15

Agent readiness — 15/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/footway/"><img src="https://apis.io/badge/footway/card.svg" alt="Footway 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 34.2 — up to +13.2 composite points
Operational Transparency scores 0.0 — up to +13.0 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/footway/apis.yml: open an issue on github.com/api-evangelist/footway 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 2

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

APIs 1

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

Footway Agent Commerce (UCP)

The footway.com storefront's agent-facing commerce surface. Built on Shopify, it implements the Universal Commerce Protocol (UCP) for agent-driven commerce: a UCP merchant profi...

MCP Servers 1

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

Footway MCP Server

Universal Commerce Protocol (UCP) MCP endpoint for the footway.com Shopify storefront. Agents use it for buyer-approved, agent-driven commerce: catalog search, cart creation, an...

MCP SERVER

Agent Skills 1

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

Buy a product on Footway as an agent (UCP)

AGENT SKILL

Security Posture 2

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

Footway Authentication

oauth2/openIdConnect · 1 scheme

SECURITY

Footway Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

Footway Scopes

4 scopes · authorizationCode

4 scopes

SCOPES

Resources

Get Started 2

Portal, sign-up, and the first successful call

DeveloperPortal

DeveloperPortal

SignUp

SignUp

Documentation 1

Reference material describing how the API behaves

Documentation

Documentation

Agent Surfaces 4

MCP servers, agent skills, and machine-readable catalogs

MCPServer

LLMsTxt

WellKnown

AgentSkill

Design & Contract 2

Pagination, idempotency, versioning, errors, and events

Conventions

Conventions

Conformance

Conformance

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 2

Pricing, plans, and the legal terms of use

TermsOfService

TermsOfService

PrivacyPolicy

PrivacyPolicy

Company 3

The organization behind the API

Blog

Blog

Website

Website

Blog

Blog

Source (apis.yml)

aid: footway
name: Footway
description: 'Footway is a Nordic, data-driven e-commerce group (Nasdaq First North Growth Market, Stockholm) that operates
  the Footway footwear-and-fashion marketplace across roughly 24 European markets, carrying around 800 brands for more than
  two million customers, alongside its Operations-as-a-Service ("ECOM IN A BOX") merchant infrastructure at footwayplus.com
  / oaas.footway.com and a merchant portal at merchant.footwayplus.com. The consumer storefront at footway.com runs on Shopify
  and exposes an agent-native commerce surface: an llms.txt / agents.md agent guide, a Universal Commerce Protocol (UCP) merchant
  profile at /.well-known/ucp, a UCP MCP endpoint for buyer-approved agent checkout, and Shopify Customer Account OpenID Connect
  / OAuth 2.0 authentication.'
url: https://raw.githubusercontent.com/api-evangelist/footway/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- northzone
x-tier: stub
x-tier-reason: portfolio-lead
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
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-10-06'
image: https://footway.com/cdn/shop/files/Namnlos_presentation_4_245a932a-42a0-441f-bdd5-b609ade84b97.svg?v=1744815789
tags:
- Company
- Consumer
- E-Commerce
- Marketplace
- Retail
- Footwear
- Fashion
- Shopify
- Agentic Commerce
- Universal Commerce Protocol
- MCP
- Nordic
tags_raw:
- Company
- Consumer
- E-commerce
- Marketplace
- Retail
- Footwear
- Fashion
- Shopify
- Agent Commerce
- UCP
- MCP
- Nordic
apis:
- name: Footway Agent Commerce (UCP)
  description: 'The footway.com storefront''s agent-facing commerce surface. Built on Shopify, it implements the Universal
    Commerce Protocol (UCP) for agent-driven commerce: a UCP merchant profile at /.well-known/ucp advertising catalog search,
    cart, checkout, fulfillment, discount and order capabilities, and a UCP MCP endpoint (/api/ucp/mcp) that agents call for
    buyer-approved checkout. Read-only product, collection and search JSON endpoints are available without authentication;
    authenticated customer flows use Shopify Customer Account OIDC/OAuth 2.0.'
  humanURL: https://footway.com/llms.txt
  baseURL: https://footway.com
  properties:
  - type: LLMsTxt
    url: llms/footway-llms.txt
  - type: MCPServer
    url: mcp/footway-mcp.yml
  - type: Authentication
    url: authentication/footway-authentication.yml
  - type: OAuthScopes
    url: scopes/footway-scopes.yml
  - type: Conventions
    url: conventions/footway-conventions.yml
  - type: Conformance
    url: conformance/footway-conformance.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://about.footway.com/en/news
  type: Blog
- type: Website
  url: https://www.footway.co.uk
- type: DeveloperPortal
  url: https://footway.com/llms.txt
- type: Documentation
  url: https://footway.com/agents.md
- type: MCPServer
  url: mcp/footway-mcp.yml
- type: LLMsTxt
  url: llms/footway-llms.txt
- type: WellKnown
  url: well-known/footway-well-known.yml
- type: Authentication
  url: authentication/footway-authentication.yml
- type: OAuthScopes
  url: scopes/footway-scopes.yml
- type: Conventions
  url: conventions/footway-conventions.yml
- type: Conformance
  url: conformance/footway-conformance.yml
- type: DomainSecurity
  url: security/footway-domain-security.yml
- type: AgentSkill
  url: skills/_index.yml
- type: Support
  url: https://footway.com/pages/contact
- type: TermsOfService
  url: https://footway.com/policies/terms-of-service
- type: PrivacyPolicy
  url: https://footway.com/policies/privacy-policy
- type: SignUp
  url: https://footway.com/account
- type: Blog
  url: https://about.footway.com
x-enrichment:
  date: '2026-07-19'
  status: backfilled
  pass: local-v1
  note: backfilled from .gitignore signal + verified work evidence

Footway API — frequently asked questions

Does Footway have an API?

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

How do I authenticate with the Footway API?

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

Does Footway have an MCP server?

Yes. APIs.io lists 1 MCP server for Footway: Universal Commerce Protocol (UCP) MCP endpoint for the footway.com Shopify storefront. Agents use it for buyer-approved, agent-driven commerce: catalog search, cart creation, and checkout. Checkout re

Is the Footway API ready for AI agents?

Footway has a Kin Score of 27.4 out of 100 (thin) and an Agent Readiness score of 14.7 (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/footway"

All providers

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

Every operation they expose

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

How their score was established

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