Afero

Afero, Inc. is a Los Altos, California IoT platform company founded in 2014 by Joe Britt and Shin Matsumura. Afero ships an end-to-end connected-product stack: ASR secure radio modules with a hardware root of trust and an embedded Hardware Security Module, the afLib MCU libraries and Secure Linux Device SDK for firmware, a Bluetooth Low Energy and Wi-Fi onboarding path, the Afero Profile Editor low-code device-modeling tool, Java (Android) and Swift (iOS) mobile SDKs with a Softhub, and the Afero Cloud — a RESTful API at api.afero.io that lists accounts and devices, reports real-time device state, executes attribute read and write actions on connected devices, and drives the over-the-air firmware pipeline. Afero has raised $73.2M from investors including Samsung Catalyst Fund and Crosspoint Capital Partners and reports millions of deployed devices across 200+ product categories in consumer, enterprise and industrial markets.

Afero publishes 4 API contracts indexed on the APIs.io network, including Cloud Authentication API, Cloud Users API, Cloud Devices API, and 1 more. Tagged areas include Company, IoT, IoT Platform, Connected Devices, and Device Management.

The Afero catalog on APIs.io includes 1 Spectral governance ruleset.

Afero’s developer surface includes authentication, documentation, API reference, getting-started guide, developer console, support, engineering blog, and 31 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

39.2/100 thin ▬ flat Agent 22/100 agent aware Front door AI 3/6 light Heartbeat 35/100 slowing saas Full breakdown ↓
scored 2026-11-13 · rubric v0.28.0 · Show this score on your site →

1 published contract 4 Agent Skills

Company IoTIoT PlatformConnected Devices Device Management Firmware Over-the-Air Updates Bluetooth Low EnergyEmbedded SecurityHardware

Kin Score

Kin Score How this is scored →
scored 2026-11-13 · rubric v0.28.0

Composite quality — 39.2/100 · thin

Contract Quality 2.6 / 19

Developer Ergonomics 9.9 / 15

Access Clarity 6.1 / 15

Operational Transparency 2.8 / 10

Contract Governance 1.6 / 9

Discoverability 5.5 / 8

Regulatory Posture 3.8 / 15

Create-or-Update Ergonomics 0.0 / 10

Agent readiness — 22/100 · agent aware

Machine-Readable Contract 18 / 18

Agentic Access Contract 10 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 7 / 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 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 0 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

Regulatory Posture applies to this provider. Its tags matched the Energy & Utilities 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 applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.

The six quality facets above are damped to 75 points between them, because the conditional facet above carries the other 25. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 75% 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/afero/"><img src="https://apis.io/badge/afero/card.svg" alt="Afero 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):

MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship Ask about this →
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) Ask about this →
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0 Ask about this →
Rate-Limit Signaling +7 pts — OpenAPI responses document X-RateLimit-* / RateLimit headers (verified), else a rate_limits artifact or RateLimits link (documented) Ask about this →
Registration Without a Human +6 pts — a `registration_endpoint` in the served RFC 8414 / OIDC discovery document Ask about this →
Delegated User Identity +6 pts — a served discovery document listing authorization_code in grant_types_supported (served), else an oauth2 authorizationCode flow or openIdConnect declared in an OpenAPI (documented) Ask about this →

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 14.1 — up to +21.5 composite points Ask about this →
Access Clarity scores 40.4 — up to +11.9 composite points Ask about this →
Contract Governance scores 18.2 — up to +9.8 composite points Ask about this →

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.

Not sure how this applies to your stack? Ask about any one item. Kin Lane reads every question, looks at your profile and your situation, and replies with what a fix would take — scoped to that one area, priced up front, yours whether you ship it or not. Ask a question →

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

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.

OpenAPI

measured — observed by APIs.io (published)

OAuth 2.0

measured — observed by APIs.io (declared)

APIs 4

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

Afero Cloud Authentication API

The OAuth 2.0 token endpoint for the Afero Cloud. A partner authenticates with HTTP Basic using the OAuth Client ID and Client Secret issued in the Afero Profile Editor, posts t...

Afero Cloud Users API

The Afero Cloud Users API returns the profile of the authenticated end-user: the Afero accounts the user can access and the privileges held on each, the sign-in credential and i...

Afero Cloud Devices API

The Afero Cloud Devices API lists the devices linked to an Afero account and, via the expansions query parameter, returns device state (available, visible, connected, connectabl...

Afero Cloud OTA Firmware API

The Afero Over-the-Air (OTA) Update API lets a partner drive firmware releases from their own CI/CD pipeline instead of the OTA Manager web application. It creates and updates p...

Open Collections 4

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

Afero Cloud Authentication API

OPEN COLLECTION

Afero Cloud Devices API

OPEN COLLECTION

Afero Cloud Firmware OTA API

OPEN COLLECTION

Afero Cloud Users API

OPEN COLLECTION

Agent Skills 4

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

Audit the firmware inventory of an Afero device type

AGENT SKILL

Control an Afero device by writing an attribute

AGENT SKILL

Publish a firmware image and push it over the air

AGENT SKILL

Read the state of the devices on an Afero account

AGENT SKILL

Terms of Service 1

What its API terms permit and prohibit, quoted from its own page.

Afero

11 quoted statements, read from Afero's own page on 2026-11-09.

TERMS

Privacy & Data 1

Its role, the data it processes, retention and transfers, quoted from its own privacy page.

Afero

11 quoted statements, read from Afero's own page on 2026-11-09.

PRIVACY

Eligibility 1

Who may sign up and where, quoted from its own terms.

Afero

2 quoted statements, read from Afero's own page on 2026-11-09.

ELIGIBILITY

Data License 1

How its data and outputs may be reused, quoted from its own terms.

Afero

1 quoted statement, read from Afero's own page on 2026-11-09.

LICENSE

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs. Counts are the severity each rule declares, not results of running them.

Afero API Rules

73 rules · 65 error-severity 7 warn-severity 1 info-severity

SPECTRAL

OpenAPI Overlays 5

Overlays applied on top of this provider's contracts. Each card says who wrote it: a document the provider publishes, or one API Evangelist derived or generated.

Afero Authentication Api Overlay

2 actions · update · afero-authentication-api-openapi.yml

DERIVED

Afero Cloud Api Overlay

4 actions · update · afero-cloud-api-openapi.yml

DERIVED

Afero Devices Api Overlay

3 actions · update · afero-devices-api-openapi.yml

DERIVED

Afero Ota Api Overlay

3 actions · update · afero-ota-api-openapi.yml

DERIVED

Afero Users Api Overlay

2 actions · update · afero-users-api-openapi.yml

DERIVED

Security Posture 3

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

Afero Authentication

http/oauth2 · 2 schemes

SECURITY

Afero Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Afero Vulnerability Disclosure

security.txt · contact published

SECURITY

Agentic Access (API Evangelist recommendations) 1

Recommended x-agentic-access execution contracts for AI agents.

Afero Agentic Access

25 operations · 12 acting

AGENTIC

Resources

Get Started 4

Portal, sign-up, and the first successful call

DeveloperPortal

DeveloperPortal

GettingStarted

GettingStarted

Console

Console

Login

Documentation 2

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

Agent Surfaces 5

MCP servers, agent skills, and machine-readable catalogs

X-MCPServerCandidate

AgenticAccess

WellKnown

LLMsTxt

AgentSkill

Design & Contract 5

Pagination, idempotency, versioning, errors, and events

Conventions

ErrorCatalog

Lifecycle

Conformance

DataModel

Build 3

SDKs, sample code, and the tooling you integrate with

GitHubOrganization

GitHubOrganization

Packages

Packages

SDKs

SDKs

Access & Security 5

Authentication, authorization, and security posture

VulnerabilityDisclosure

VulnerabilityDisclosure

DomainSecurity

Authentication

SecurityTxt

Security

Operate 3

Status, limits, changes, and where to get help

Support

Support

ChangeLog

ChangeLog

ReleaseNotes

ReleaseNotes

Commercial 4

Pricing, plans, and the legal terms of use

TermsOfService

PrivacyPolicy

UsageTerms

DataLicense

Company 3

The organization behind the API

Website

Website

Blog

Blog

LinkedIn

Other 4

Properties that don't map to a standard resource type

WhitePapers

Overlay

DataProcessing

Eligibility

Source (apis.yml)

aid: afero
name: Afero
description: 'Afero, Inc. is a Los Altos, California IoT platform company founded in 2014 by Joe Britt and Shin Matsumura.
  Afero ships an end-to-end connected-product stack: ASR secure radio modules with a hardware root of trust and an embedded
  Hardware Security Module, the afLib MCU libraries and Secure Linux Device SDK for firmware, a Bluetooth Low Energy and Wi-Fi
  onboarding path, the Afero Profile Editor low-code device-modeling tool, Java (Android) and Swift (iOS) mobile SDKs with
  a Softhub, and the Afero Cloud — a RESTful API at api.afero.io that lists accounts and devices, reports real-time device
  state, executes attribute read and write actions on connected devices, and drives the over-the-air firmware pipeline. Afero
  has raised $73.2M from investors including Samsung Catalyst Fund and Crosspoint Capital Partners and reports millions of
  deployed devices across 200+ product categories in consumer, enterprise and industrial markets.'
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: true
  label: Hosted service · you call their endpoint
  confidence: high
  source:
  - openapi
  - 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
  - security
  generated: '2026-11-13'
  method: derived
image: https://cdn.afero.io/social/afero_logo_114x114.png
url: https://raw.githubusercontent.com/api-evangelist/afero/refs/heads/main/apis.yml
x-type: company
x-source: harvest:secondary-market
specificationVersion: '0.23'
created: '2026-08-02'
modified: '2026-08-02'
x-docs-platform: mkdocs
x-docs-platform-confidence: medium
x-docs-platform-checked: 2026-09-17
tags:
- Company
- IoT
- IoT Platform
- Connected Devices
- Device Management
- Firmware
- Over-the-Air Updates
- Bluetooth Low Energy
- Embedded Security
- Hardware
tags_raw:
- Company
- Internet of Things
- IoT Platform
- Connected Devices
- Device Management
- Firmware
- Over-the-Air Updates
- Bluetooth Low Energy
- Embedded Security
- Hardware
apis:
- aid: afero:authentication-api
  name: Afero Cloud Authentication API
  description: The OAuth 2.0 token endpoint for the Afero Cloud. A partner authenticates with HTTP Basic using the OAuth Client
    ID and Client Secret issued in the Afero Profile Editor, posts the end-user credentials with grant_type=password, and
    receives a bearer access token (scope "partner account") that expires in approximately four hours and is sent on every
    subsequent Afero Cloud API request.
  humanURL: https://afero-docs.readthedocs.io/en/latest/API-OAuthEndpoints/
  baseURL: https://api.afero.io
  tags:
  - Authentication
  - OAuth
  - Security
  tags_raw:
  - Authentication
  - OAuth
  - Security
  properties:
  - type: OpenAPI
    url: openapi/afero-authentication-api-openapi.yml
  - type: Documentation
    url: https://afero-docs.readthedocs.io/en/latest/API-OAuthEndpoints/
  - type: Overlay
    url: overlays/afero-authentication-api-overlay.yaml
- aid: afero:users-api
  name: Afero Cloud Users API
  description: 'The Afero Cloud Users API returns the profile of the authenticated end-user: the Afero accounts the user can
    access and the privileges held on each, the sign-in credential and its verification state, any partner accounts and partner
    privileges (invite users, manage device profiles, view device info), and the user, developer and general terms-of-service
    versions accepted or awaiting acceptance.'
  humanURL: https://afero-docs.readthedocs.io/en/latest/API-UserEndpoints/
  baseURL: https://api.afero.io
  tags:
  - User
  - Account
  - Identity
  tags_raw:
  - Users
  - Accounts
  - Identity
  properties:
  - type: OpenAPI
    url: openapi/afero-users-api-openapi.yml
  - type: Documentation
    url: https://afero-docs.readthedocs.io/en/latest/API-UserEndpoints/
  - type: Overlay
    url: overlays/afero-users-api-overlay.yaml
- aid: afero:devices-api
  name: Afero Cloud Devices API
  description: The Afero Cloud Devices API lists the devices linked to an Afero account and, via the expansions query parameter,
    returns device state (available, visible, connected, connectable, linked, RSSI, location), system and partner device tags,
    or the raw device attribute values. It also executes asynchronous attribute_read and attribute_write actions against a
    device by attribute ID with hexadecimal little-endian payloads, and updates a device friendly name.
  humanURL: https://afero-docs.readthedocs.io/en/latest/API-DeviceEndpoints/
  baseURL: https://api.afero.io
  tags:
  - Devices
  - Device Management
  - IoT
  - Telemetry
  tags_raw:
  - Devices
  - Device Management
  - Internet of Things
  - Telemetry
  properties:
  - type: OpenAPI
    url: openapi/afero-devices-api-openapi.yml
  - type: Documentation
    url: https://afero-docs.readthedocs.io/en/latest/API-DeviceEndpoints/
  - type: Overlay
    url: overlays/afero-devices-api-overlay.yaml
  - type: AgentSkill
    url: skills/afero-read-device-state.md
  - type: AgentSkill
    url: skills/afero-control-a-device.md
- aid: afero:ota-api
  name: Afero Cloud OTA Firmware API
  description: The Afero Over-the-Air (OTA) Update API lets a partner drive firmware releases from their own CI/CD pipeline
    instead of the OTA Manager web application. It creates and updates partner firmware types, creates firmware records in
    the partner firmware pool, uploads firmware binaries to a temporary location and moves them into the permanent repository,
    checks whether a name and version already exists, associates pool images with device types to make them OTA-eligible,
    lists and filters firmware images with tag filtering and paging, pushes an image to a specific device, dissociates an
    image from a device type, and lists firmware tags.
  humanURL: https://afero-docs.readthedocs.io/en/latest/API-OTAEndpoints/
  baseURL: https://api.afero.io
  tags:
  - Firmware
  - Over-the-Air Updates
  - Device Management
  - Deployment
  properties:
  - type: OpenAPI
    url: openapi/afero-ota-api-openapi.yml
  - type: Documentation
    url: https://afero-docs.readthedocs.io/en/latest/API-OTAEndpoints/
  - type: APIReference
    url: https://afero-docs.readthedocs.io/en/latest/API-OTAEndpoints-Funcs/
  - type: Overlay
    url: overlays/afero-ota-api-overlay.yaml
  - type: AgentSkill
    url: skills/afero-publish-firmware-ota.md
  - type: AgentSkill
    url: skills/afero-audit-firmware-fleet.md
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: X-MCPServerCandidate
  url: mcp/afero-mcp.yml
  note: 'Renamed from MCPServer 2026-09-03 (roadmap#247): the manifest self-describes as status: candidate — a tool list derived
    from the published API contracts, not an existing server. The scorer already read the manifest and reported mcp_server
    correctly; the MCPServer type was crediting the artifact-type surfaces with a server that does not exist.'
- type: AgenticAccess
  url: agentic-access/afero-agentic-access.yml
- type: VulnerabilityDisclosure
  url: security/afero-vulnerability-disclosure.yml
- type: DomainSecurity
  url: security/afero-domain-security.yml
- type: Authentication
  url: authentication/afero-authentication.yml
- type: Website
  url: https://www.afero.io/
- type: DeveloperPortal
  url: https://afero-docs.readthedocs.io/en/latest/
- type: Documentation
  url: https://afero-docs.readthedocs.io/en/latest/
- type: APIReference
  url: https://afero-docs.readthedocs.io/en/latest/CloudAPIs/
- type: GettingStarted
  url: https://afero-docs.readthedocs.io/en/latest/Tutorials/
- type: Console
  url: https://console.afero.io/
- type: Login
  url: https://console.afero.io/
- type: Support
  url: https://www.afero.io/html/home/contact-afero.html
- type: GitHubOrganization
  url: https://github.com/aferodeveloper
- type: Blog
  url: https://www.afero.io/html/home/news.html
- type: WhitePapers
  url: https://www.afero.io/html/home/whitepapers.html
- type: TermsOfService
  url: https://cdn.afero.io/tos/developer/v1/developer.html
- type: PrivacyPolicy
  url: https://www.afero.io/html/home/privacy.html
- type: LinkedIn
  url: https://www.linkedin.com/company/afero
- type: Packages
  url: packages/afero-packages.yml
- type: SDKs
  url: packages/afero-packages.yml
- type: WellKnown
  url: well-known/afero-well-known.yml
- type: SecurityTxt
  url: well-known/afero-security.txt
- type: LLMsTxt
  url: llms/afero-llms.txt
- type: Conventions
  url: conventions/afero-conventions.yml
- type: ErrorCatalog
  url: errors/afero-problem-types.yml
- type: Lifecycle
  url: lifecycle/afero-lifecycle.yml
- type: ChangeLog
  url: changelog/afero-changelog.yml
- type: Conformance
  url: conformance/afero-conformance.yml
- type: DataModel
  url: data-model/afero-data-model.yml
- type: AgentSkill
  url: skills/_index.yml
- type: Security
  url: https://afero.io/html/home/VDP.html
- type: ReleaseNotes
  url: https://afero-docs.readthedocs.io/en/latest/RelNotes/
- type: Overlay
  url: overlays/afero-cloud-api-overlay.yaml
- type: UsageTerms
  url: terms/afero-terms-of-service.yml
- type: DataProcessing
  url: privacy/afero-privacy-policy.yml
- type: Eligibility
  url: eligibility/afero-eligibility.yml
- type: DataLicense
  url: data-license/afero-data-license.yml
x-forge-listing: https://forgeglobal.com/afero_stock/
x-enrichment:
  date: '2026-08-02'
  status: enriched
  artifacts_added: 30
  pass: local-v1

Afero API — frequently asked questions

Does Afero have an API?

Yes. APIs.io lists 4 APIs from Afero, including Afero Cloud Authentication API, Afero Cloud Users API and Afero Cloud Devices API, and 1 more.

Is there an OpenAPI specification for the Afero API?

Yes. APIs.io indexes 4 OpenAPI specifications for Afero, each linked for download from this page.

How do I authenticate with the Afero API?

Afero uses bearer-token authentication (http/oauth2 · 2 schemes). The details are profiled on APIs.io as Afero Authentication.

Is the Afero API ready for AI agents?

Afero has a Kin Score of 39.2 out of 100 (thin) and an Agent Readiness score of 22.3 (agent-aware), scored by API Evangelist on 2026-11-13.

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/afero"

All providers

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

Every operation they expose

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

How their score was established

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