Autopass website screenshot

Autopass

Autopass ("快速通") is a Taiwan-based mobility financial-services platform that connects service locations, car-owner apps, payments and benefits so that every driver enjoys a fast, convenient driving experience. Through its "powered by Autopass" service-authorization program, channel brand partners embed license-plate-based parking payment into their own car-owner apps: they register user license plates, surface partner parking locations (POIs) with live rates and hours, read in-progress parking sessions and completed orders, and receive entry/exit/billing/refund notifications over an OAuth 2.0 / OpenID Connect secured API. Autopass aims to become Asia's largest provider of mobility financial services. Backed by 500 Global.

Autopass publishes 3 APIs on the APIs.io network: Locations API, Orders API, and Sessions API. Tagged areas include Company, Mobility, Parking, Payments, and Automotive.

The Autopass catalog on APIs.io includes 1 event-driven AsyncAPI specification.

Autopass’ developer surface includes documentation, API reference, authentication, and 15 more developer resources.

42.2/100 developing ▬ flat Agent 36/100 agent ready Full breakdown ↓
scored 2026-08-20 · rubric v0.12.0
AccessSelf serve
3 APIs 1 MCP Servers
CompanyMobilityParkingPaymentsAutomotiveFinancial-ServicesAuthenticationTaiwan

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-08-20 · rubric v0.12.0
Composite quality — 42.2/100 · developing
Contract Quality 13.7 / 21
Developer Ergonomics 6.8 / 17
Access Clarity 3.6 / 17
Operational Transparency 0.9 / 11
Contract Governance 1.2 / 10
Discoverability 7.9 / 9
Regulatory Posture 7.0 / 15
Agent readiness — 36/100 · agent ready
Machine-Readable Contract 18 / 18
Agentic Access Contract 0 / 10
Documented Reversibility 6 / 6
MCP Server 0 / 12
Machine-Readable Auth 10 / 10
Idempotency 9 / 9
Stable Error Semantics 0 / 8
Request/Response Examples 0 / 7
Rate-Limit Signaling 0 / 7
Typed Event Surface 6 / 6
Agent Skills 5 / 5
Well-Known Catalog 0 / 4
Consent & Bot Identity 0 / 3
A2A Agent Card 0 / 8
Dry-Run / Simulate Mode 4 / 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/autopass: open an issue to ask a question, or submit a pull request to add artifacts. Want it done for you? Prioritized profiling — $2,500 →

APIs 3

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

Autopass Locations API

Partner parking locations (POIs)

Autopass Orders API

Completed parking transactions and invoices

Autopass Sessions API

In-progress parking sessions

Open Collections 4

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

API Collection

OPEN COLLECTION

MCP Servers 1

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

Event Specifications 1

AsyncAPI definitions for this provider's event-driven and streaming APIs.

Security Posture 2

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

Autopass Authentication

oauth2/openIdConnect · 2 schemes

SECURITY

Autopass Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

Autopass Scopes

1 scope · authorizationCode/clientCredentials

1 scopes

SCOPES

Resources

Get Started 1

Portal, sign-up, and the first successful call

Documentation 2

Reference material describing how the API behaves

Agent Surfaces 4

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 4

Pagination, idempotency, versioning, errors, and events

Access & Security 3

Authentication, authorization, and security posture

Commercial 2

Pricing, plans, and the legal terms of use

Company 1

The organization behind the API

Other 1

Properties that don't map to a standard resource type

Source (apis.yml)

apis.yml Raw ↑
aid: autopass
name: Autopass
description: 'Autopass ("快速通") is a Taiwan-based mobility financial-services platform that connects service locations, car-owner
  apps, payments and benefits so that every driver enjoys a fast, convenient driving experience. Through its "powered by Autopass"
  service-authorization program, channel brand partners embed license-plate-based parking payment into their own car-owner
  apps: they register user license plates, surface partner parking locations (POIs) with live rates and hours, read in-progress
  parking sessions and completed orders, and receive entry/exit/billing/refund notifications over an OAuth 2.0 / OpenID Connect
  secured API. Autopass aims to become Asia''s largest provider of mobility financial services. Backed by 500 Global.'
url: https://raw.githubusercontent.com/api-evangelist/autopass/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- 500-global
x-tier: stub
x-tier-reason: portfolio-lead
accessModel:
  pricing: unknown
  onboarding: self-serve
  trial: false
  try_now: false
  public: false
  label: Self-serve signup
  confidence: medium
  source:
  - authentication
  generated: '2026-07-22'
  method: derived
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-07-18'
image: https://www.autopass.xyz/autopass_og.jpg
tags:
- Company
- Mobility
- Parking
- Payments
- Automotive
- Financial-Services
- Authentication
- Taiwan
tags_raw:
- Company
- Mobility
- Parking
- Payments
- Automotive
- Financial Services
- OAuth
- Taiwan
apis:
- aid: autopass:autopass-locations-api
  name: Autopass Locations API
  description: Partner parking locations (POIs)
  humanURL: https://docs.autopass.xyz
  baseURL: https://api.autopass.xyz
  tags:
  - Locations
  properties:
  - type: OpenAPI
    url: openapi/autopass-locations-api-openapi.yml
  - type: Authentication
    url: authentication/autopass-authentication.yml
  - type: OAuthScopes
    url: scopes/autopass-scopes.yml
  - type: Conventions
    url: conventions/autopass-conventions.yml
  - type: DataModel
    url: data-model/autopass-data-model.yml
  - type: Webhooks
    url: asyncapi/autopass-webhooks.yml
- aid: autopass:autopass-orders-api
  name: Autopass Orders API
  description: Completed parking transactions and invoices
  humanURL: https://docs.autopass.xyz
  baseURL: https://api.autopass.xyz
  tags:
  - Order
  tags_raw:
  - Orders
  properties:
  - type: OpenAPI
    url: openapi/autopass-orders-api-openapi.yml
  - type: Authentication
    url: authentication/autopass-authentication.yml
  - type: OAuthScopes
    url: scopes/autopass-scopes.yml
  - type: Conventions
    url: conventions/autopass-conventions.yml
  - type: DataModel
    url: data-model/autopass-data-model.yml
  - type: Webhooks
    url: asyncapi/autopass-webhooks.yml
- aid: autopass:autopass-sessions-api
  name: Autopass Sessions API
  description: In-progress parking sessions
  humanURL: https://docs.autopass.xyz
  baseURL: https://api.autopass.xyz
  tags:
  - Sessions
  properties:
  - type: OpenAPI
    url: openapi/autopass-sessions-api-openapi.yml
  - type: Authentication
    url: authentication/autopass-authentication.yml
  - type: OAuthScopes
    url: scopes/autopass-scopes.yml
  - type: Conventions
    url: conventions/autopass-conventions.yml
  - type: DataModel
    url: data-model/autopass-data-model.yml
  - type: Webhooks
    url: asyncapi/autopass-webhooks.yml
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: Overlay
  url: overlays/autopass-overlay.yaml
- type: DomainSecurity
  url: security/autopass-domain-security.yml
- type: Website
  url: https://en.autopass.xyz
- type: DeveloperPortal
  url: https://docs.autopass.xyz
- type: Documentation
  url: https://docs.autopass.xyz
- type: APIReference
  url: https://docs.autopass.xyz/llms.txt
- type: Authentication
  url: authentication/autopass-authentication.yml
- type: OAuthScopes
  url: scopes/autopass-scopes.yml
- type: WellKnown
  url: well-known/autopass-well-known.yml
- type: LLMsTxt
  url: llms/autopass-llms.txt
- type: Conventions
  url: conventions/autopass-conventions.yml
- type: DataModel
  url: data-model/autopass-data-model.yml
- type: Lifecycle
  url: lifecycle/autopass-lifecycle.yml
- type: Webhooks
  url: asyncapi/autopass-webhooks.yml
- type: MCPServer
  url: mcp/autopass-mcp.yml
- type: AgentSkill
  url: skills/_index.yml
- type: TermsOfService
  url: https://autopass.xyz/terms
- type: PrivacyPolicy
  url: https://autopass.xyz/privacy
x-enrichment:
  date: '2026-07-19'
  status: backfilled
  pass: local-v1
  note: backfilled from .gitignore signal + verified work evidence