Zamna

Zamna is a GDPR-compliant digital identity and passenger-data verification platform for the aviation and travel industry, used by airlines, airports, ground handlers and governments to verify passport, visa and health documents before a traveler reaches the airport. Its Ready To Fly (PaxCheck) API stitches passenger sessions, document recognition and consent capture into airline systems, while the Checklist API resolves live travel rules into localized, per-passenger requirements and a pluggable WebView drives the MMB/OLCI flows. Zamna has verified over 60 million travel identities across 179+ countries and integrates with airline PSS/DCS platforms such as Amadeus Altea, Navitaire and Sabre.

Zamna publishes 4 API contracts indexed on the APIs.io network, including Session API, Start API, Start With Booking Id And Surname API, and 1 more. Tagged areas include Company, Aviation, Travel, Identity Verification, and Digital Identity.

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

Zamna’s developer surface includes authentication, documentation, API reference, getting-started guide, sandbox, and 13 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

32.0/100 thin ▬ flat Agent 24/100 agent aware Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

1 published contract 1 Agent Skills

Company Aviation Travel Identity Verification Digital IdentityPassenger ProcessingAirlinesBorder SecurityDocument Verification KYC

Kin Score

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

Composite quality — 32.0/100 · thin

Contract Quality 8.4 / 19

Developer Ergonomics 8.8 / 15

Access Clarity 0.0 / 15

Operational Transparency 0.0 / 10

Contract Governance 1.6 / 9

Discoverability 5.5 / 8

Regulatory Posture 2.5 / 15

Create-or-Update Ergonomics 0.0 / 10

Agent readiness — 24/100 · agent aware

Machine-Readable Contract 18 / 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 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 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 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/zamna/"><img src="https://apis.io/badge/zamna/card.svg" alt="Zamna 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
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)
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)
Registration Without a Human +6 pts — a `registration_endpoint` in the served RFC 8414 / OIDC discovery document

8 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Access Clarity scores 0.0 — up to +20.0 composite points
Contract Quality scores 44.7 — up to +13.8 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/zamna/apis.yml: open an issue on github.com/api-evangelist/zamna 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
Biometrics Testing (biometric recognition vendors, identity verification depth)	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 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.

OpenAPI

measured — observed by APIs.io (published)

APIs 4

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

Zamna Session API

The Session API from Zamna — 9 operation(s) for session.

Zamna Start API

The Start API from Zamna — 1 operation(s) for start.

Zamna Start With Booking Id And Surname API

The Start With Booking Id And Surname API from Zamna — 1 operation(s) for start with booking id and surname.

Zamna Start2 API

The Start2 API from Zamna — 1 operation(s) for start2.

Open Collections 4

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

Zamna Ready To Fly Session API

OPEN COLLECTION

Zamna Ready To Fly Session Start API

OPEN COLLECTION

Zamna Ready To Fly Session Start With Booking Id And Surname API

OPEN COLLECTION

Zamna Ready To Fly Session Start2 API

OPEN COLLECTION

Agent Skills 1

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

Complete a Ready To Fly passenger check

AGENT SKILL

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs.

Zamna API Rules

42 rules · 36 errors 4 warnings 2 info

SPECTRAL

OpenAPI Overlays 1

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.

Zamna Paxcheck Overlay

3 actions · documentation · zamna-paxcheck-openapi-original.json

DERIVED

Security Posture 2

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

Zamna Authentication

http · 1 scheme

SECURITY

Zamna Domain Security

TLSv1.3 · DMARC

SECURITY

Resources

Get Started 3

Portal, sign-up, and the first successful call

DeveloperPortal

DeveloperPortal

GettingStarted

GettingStarted

Sandbox

Sandbox

Documentation 2

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

Agent Surfaces 3

MCP servers, agent skills, and machine-readable catalogs

X-MCPServerCandidate

X-MCPServerCandidate

AgentSkill

AgentSkill

LLMsTxt

LLMsTxt

Design & Contract 6

Pagination, idempotency, versioning, errors, and events

Conformance

ErrorCatalog

Lifecycle

Conventions

Components

DataModel

Access & Security 2

Authentication, authorization, and security posture

DomainSecurity

DomainSecurity

Authentication

Authentication

Company 1

The organization behind the API

Website

Website

Other 1

Properties that don't map to a standard resource type

Overlay

Overlay

Source (apis.yml)

aid: zamna
deliveryModel:
  model: unknown
  open_source: false
  commercial: false
  callable_host: true
  label: Delivery model not determined — needs a product licence on record
  confidence: low
  source:
  - openapi
  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
  - sandbox
  generated: '2026-11-06'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/zamna.png
name: Zamna
description: Zamna is a GDPR-compliant digital identity and passenger-data verification platform for the aviation and travel
  industry, used by airlines, airports, ground handlers and governments to verify passport, visa and health documents before
  a traveler reaches the airport. Its Ready To Fly (PaxCheck) API stitches passenger sessions, document recognition and consent
  capture into airline systems, while the Checklist API resolves live travel rules into localized, per-passenger requirements
  and a pluggable WebView drives the MMB/OLCI flows. Zamna has verified over 60 million travel identities across 179+ countries
  and integrates with airline PSS/DCS platforms such as Amadeus Altea, Navitaire and Sabre.
url: https://raw.githubusercontent.com/api-evangelist/zamna/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- seedcamp
x-tier: stub
x-tier-reason: portfolio-lead
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-07-21'
tags:
- Company
- Aviation
- Travel
- Identity Verification
- Digital Identity
- Passenger Processing
- Airlines
- Border Security
- Document Verification
- KYC
apis:
- aid: zamna:zamna-session-api
  name: Zamna Session API
  description: The Session API from Zamna — 9 operation(s) for session.
  humanURL: https://dev.zamna.com/paxcheck/
  baseURL: https://paxcheck-app-dev.staging.zamna.com
  tags:
  - Sessions
  tags_raw:
  - Session
  properties:
  - type: OpenAPI
    url: openapi/zamna-session-api-openapi.yml
  - type: Documentation
    url: https://dev.zamna.com/paxcheck/
  - type: InteractiveDocumentation
    url: https://paxcheck-app-dev.staging.zamna.com/swagger
- aid: zamna:zamna-start-api
  name: Zamna Start API
  description: The Start API from Zamna — 1 operation(s) for start.
  humanURL: https://dev.zamna.com/paxcheck/
  baseURL: https://paxcheck-app-dev.staging.zamna.com
  tags:
  - Start
  properties:
  - type: OpenAPI
    url: openapi/zamna-start-api-openapi.yml
  - type: Documentation
    url: https://dev.zamna.com/paxcheck/
  - type: InteractiveDocumentation
    url: https://paxcheck-app-dev.staging.zamna.com/swagger
- aid: zamna:zamna-start-with-booking-id-and-surname-api
  name: Zamna Start With Booking Id And Surname API
  description: The Start With Booking Id And Surname API from Zamna — 1 operation(s) for start with booking id and surname.
  humanURL: https://dev.zamna.com/paxcheck/
  baseURL: https://paxcheck-app-dev.staging.zamna.com
  tags:
  - Start With Booking Id And Surname
  properties:
  - type: OpenAPI
    url: openapi/zamna-start-with-booking-id-and-surname-api-openapi.yml
  - type: Documentation
    url: https://dev.zamna.com/paxcheck/
  - type: InteractiveDocumentation
    url: https://paxcheck-app-dev.staging.zamna.com/swagger
- aid: zamna:zamna-start2-api
  name: Zamna Start2 API
  description: The Start2 API from Zamna — 1 operation(s) for start2.
  humanURL: https://dev.zamna.com/paxcheck/
  baseURL: https://paxcheck-app-dev.staging.zamna.com
  tags:
  - Start2
  properties:
  - type: OpenAPI
    url: openapi/zamna-start2-api-openapi.yml
  - type: Documentation
    url: https://dev.zamna.com/paxcheck/
  - type: InteractiveDocumentation
    url: https://paxcheck-app-dev.staging.zamna.com/swagger
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: DomainSecurity
  url: security/zamna-domain-security.yml
- type: Authentication
  url: authentication/zamna-authentication.yml
- type: Website
  url: http://zamna.com
- type: DeveloperPortal
  url: https://dev.zamna.com/
- type: Documentation
  url: https://dev.zamna.com/
- type: APIReference
  url: https://paxcheck-app-dev.staging.zamna.com/swagger
- type: GettingStarted
  url: https://dev.zamna.com/start/
- type: X-MCPServerCandidate
  url: mcp/zamna-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: AgentSkill
  url: skills/_index.yml
- type: LLMsTxt
  url: llms/zamna-llms.txt
- type: Overlay
  url: overlays/zamna-paxcheck-overlay.yaml
- type: Conformance
  url: conformance/zamna-conformance.yml
- type: ErrorCatalog
  url: errors/zamna-problem-types.yml
- type: Lifecycle
  url: lifecycle/zamna-lifecycle.yml
- type: Conventions
  url: conventions/zamna-conventions.yml
- type: Sandbox
  url: sandbox/zamna-sandbox.yml
- type: Components
  url: components/zamna-components.yml
- type: DataModel
  url: data-model/zamna-data-model.yml
x-enrichment:
  date: '2026-07-21'
  status: enriched
  artifacts_added: 15
  pass: local-v1

Zamna API — frequently asked questions

Does Zamna have an API?

Yes. APIs.io lists 4 APIs from Zamna, including Zamna Session API, Zamna Start API and Zamna Start With Booking Id And Surname API, and 1 more.

Is there an OpenAPI specification for the Zamna API?

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

How do I authenticate with the Zamna API?

Zamna uses bearer-token authentication (http · 1 scheme). The details are profiled on APIs.io as Zamna Authentication.

Is the Zamna API ready for AI agents?

Zamna has a Kin Score of 32.0 out of 100 (thin) and an Agent Readiness score of 23.8 (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/zamna"

All providers

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

Every operation they expose

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

How their score was established

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