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 📡 Source on GitHub

18.4/100 emerging ▬ flat Agent 9/100 agent aware Full breakdown ↓
scored 2026-08-17 · rubric v0.11.0

0 APIs

CompanyComputer VisionRetailAutonomous CheckoutSpatial IntelligenceArtificial IntelligenceAnalyticsIdentityFraud PreventionPoint of Sale

Kin Score

Kin Score How this is scored →
scored 2026-08-17 · rubric v0.11.0

Composite quality — 18.4/100 · emerging

Contract Quality 0.0 / 21

Developer Ergonomics 2.2 / 17

Commercial Clarity 1.8 / 17

Operational Transparency 0.0 / 11

Governance 1.3 / 10

Discoverability 5.8 / 9

Regulatory Posture 7.3 / 15

Agent readiness — 9/100 · agent aware

Machine-Readable Contract 0 / 18

Agentic Access Contract 0 / 10

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

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.

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/.

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/aifi: open an issue to ask a question, or submit a pull request to add artifacts. Want it done for you? Prioritized profiling — $2,500 →

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.
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.20'
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
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'