AiFi

AiFi is a spatial-intelligence platform that uses camera-only computer vision to understand human behavior in physical spaces. Founded in 2016 and headquartered in San Francisco, it powers autonomous checkout, frictionless identity and entry, real-time fraud prevention, historical journey analytics and an operational co-pilot across retail, stadiums and arenas, quick-service restaurants, travel hubs, healthcare, campuses and government border control. The platform needs no shelf sensors or RFID and tracks shoppers with anonymous skeletal keypoint detection rather than facial recognition by default. AiFi publishes a suite of retailer-facing OASIS APIs that bridge its platform to POS (NCR, Oracle, Square) and payment (Stripe, Adyen) systems, but the developer documentation is served only to authenticated accounts through an AiFi Keycloak single sign-on.

AiFi is profiled on the APIs.io network. Tagged areas include Company, Computer Vision, Retail, Autonomous Checkout, and Spatial Intelligence.

AiFi’s developer surface includes engineering blog, authentication, and 13 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

13.7/100 emerging ▬ flat Agent 15/100 agent aware Front door AI 4/6 moderate Heartbeat 25/100 dormant Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

0 APIs

Company Computer Vision RetailAutonomous CheckoutSpatial Intelligence Artificial Intelligence Analytics Identity Fraud Prevention Point-of-Sale

Kin Score

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

Composite quality — 13.7/100 · emerging

Contract Quality 0.0 / 21

Developer Ergonomics 2.4 / 17

Access Clarity 1.8 / 17

Operational Transparency 0.0 / 11

Contract Governance 1.9 / 10

Discoverability 4.8 / 9

Regulatory Posture 3.9 / 15

Agent readiness — 15/100 · agent aware

Machine-Readable Contract 0 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 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 0 / 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 6 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 5 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

Regulatory Posture applies to this provider. Its tags matched the Payments 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/aifi/"><img src="https://apis.io/badge/aifi/card.svg" alt="AiFi 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
MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship
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

10 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 10.5 — up to +17.9 composite points
Developer Ergonomics scores 14.3 — up to +17.1 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/aifi/apis.yml: open an issue on github.com/api-evangelist/aifi 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
ONVIF Video Analytics (video surveillance, edge cameras, computer vision)	distribution	9.6 (thin)	-	-

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 1

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.

Dynamic Client Registration

measured — observed by APIs.io (published)

Security Posture 2

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

Aifi Authentication

openIdConnect/oauth2 · 1 scheme

SECURITY

Aifi Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

Aifi Scopes

10 scopes · authorizationCode/clientCredentials/deviceCode

10 scopes

SCOPES

Resources

Agent Surfaces 2

MCP servers, agent skills, and machine-readable catalogs

LLMsTxt

LLMsTxt

WellKnown

WellKnown

Design & Contract 1

Pagination, idempotency, versioning, errors, and events

Conformance

Conformance

Access & Security 3

Authentication, authorization, and security posture

DomainSecurity

DomainSecurity

Authentication

Authentication

OAuthScopes

OAuthScopes

Operate 1

Status, limits, changes, and where to get help

Contact

Contact

Commercial 1

Pricing, plans, and the legal terms of use

PrivacyPolicy

PrivacyPolicy

Company 5

The organization behind the API

Website

About

Blog

Press

Partners

Other 2

Properties that don't map to a standard resource type

OpenSourcePolicy

OpenSourcePolicy

OpenIDConnect

OpenIDConnect

Source (apis.yml)

aid: aifi
name: AiFi
description: AiFi is a spatial-intelligence platform that uses camera-only computer vision to understand human behavior in
  physical spaces. Founded in 2016 and headquartered in San Francisco, it powers autonomous checkout, frictionless identity
  and entry, real-time fraud prevention, historical journey analytics and an operational co-pilot across retail, stadiums
  and arenas, quick-service restaurants, travel hubs, healthcare, campuses and government border control. The platform needs
  no shelf sensors or RFID and tracks shoppers with anonymous skeletal keypoint detection rather than facial recognition by
  default. AiFi publishes a suite of retailer-facing OASIS APIs that bridge its platform to POS (NCR, Oracle, Square) and
  payment (Stripe, Adyen) systems, but the developer documentation is served only to authenticated accounts through an AiFi
  Keycloak single sign-on.
deliveryModel:
  model: unknown
  open_source: false
  commercial: false
  callable_host: false
  label: Delivery model not determined — needs a product licence on record
  confidence: low
  source:
  - none
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  probe_state: gated
  source:
  - authentication
  - scopes
  - security
  generated: '2026-11-06'
  method: derived
image: https://framerusercontent.com/assets/5f5E5VdygR6bvI2EpHrCRo6Euo.png
url: https://raw.githubusercontent.com/api-evangelist/aifi/refs/heads/main/apis.yml
x-type: company
x-source: harvest:secondary-market
specificationVersion: '0.23'
created: '2026-08-06'
modified: '2026-08-06'
tags:
- Company
- Computer Vision
- Retail
- Autonomous Checkout
- Spatial Intelligence
- Artificial Intelligence
- Analytics
- Identity
- Fraud Prevention
- Point-of-Sale
tags_raw:
- Company
- Computer Vision
- Retail
- Autonomous Checkout
- Spatial Intelligence
- Artificial Intelligence
- Analytics
- Identity
- Fraud Prevention
- Point of Sale
- Computer-Vision
apis: []
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: DomainSecurity
  url: security/aifi-domain-security.yml
- type: Website
  url: https://www.aifi.com/
- type: About
  url: https://www.aifi.com/about-us
- type: Blog
  url: https://www.aifi.com/blog
- type: Press
  url: https://www.aifi.com/press-coverage
- type: Partners
  url: https://www.aifi.com/partners
- type: PrivacyPolicy
  url: https://www.aifi.com/privacy
- type: Contact
  url: https://www.aifi.com/lets-talk
- type: OpenSourcePolicy
  url: https://www.aifi.com/open-source
- type: LLMsTxt
  url: llms/aifi-llms.txt
- type: WellKnown
  url: well-known/aifi-well-known.yml
- type: Authentication
  url: authentication/aifi-authentication.yml
- type: OpenIDConnect
  url: https://auth.aifi.com/realms/aifi/.well-known/openid-configuration
- type: OAuthScopes
  url: scopes/aifi-scopes.yml
- type: Conformance
  url: conformance/aifi-conformance.yml
x-enrichment:
  date: '2026-08-06'
  status: minimal
  artifacts_added: 7
  pass: local-v1
x-coverage:
  state: gated
  reason: partner-login
  detail: AiFi markets a suite of OASIS retailer APIs, but docs.aifi.com sits behind an oauth2-proxy that 302s every single
    path — including /openapi.json and every /.well-known/ path — to an AiFi Keycloak login (realm `aifi`, client_id `docs-oidc-client`),
    and www.aifi.com carries no developer, docs or API page at all, so not one line of the API reference or contract is publicly
    readable.
  evidence:
  - url: https://docs.aifi.com/openapi.json
    status: 302
  - url: https://docs.aifi.com/
    status: 302
  - url: https://www.aifi.com/developers
    status: 404
  - url: https://www.aifi.com/openapi.json
    status: 404
  - url: https://auth.aifi.com/realms/aifi/.well-known/openid-configuration
    status: 200
  checked: '2026-08-06'

AiFi API — frequently asked questions

How do I authenticate with the AiFi API?

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

Is the AiFi API ready for AI agents?

AiFi has a Kin Score of 13.7 out of 100 (emerging) and an Agent Readiness score of 15.1 (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/aifi"

All providers

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

Every operation they expose

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

How their score was established

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