Skip to main content
Use Plate Recognizer through Corsair: one client, typed API calls, local DB sync. Auth is Authorization: Token <key>, not Bearer; the key is on the Snapshot Cloud dashboard. A missing or wrong token returns HTTP 403. Each plates.read uses one Snapshot lookup and each ocr.read one OCR call from the plan’s monthly allowance. Plate text is not stored, because a plate is not a stable id. Snapshot usage is stored per year and month. OCR is a separate Plate Recognizer product: an account without it gets 403 from ocr.read. What you get:
  • 4 typed API operations
  • 1 synced entity (usage) for fast .search() / .list()

Setup

1

Install

2

Add the plugin

corsair.ts
With multiTenancy: true, scope calls with corsair.withTenant(id). See Quick start for KEK + Hub keys, and Multi-tenancy for account isolation.
3

Choose authentication

4

Connect a tenant

Mint a connect link and send the tenant to it. Hub hosts the page and delivers the result to your app — see Connect / OAuth.

Example API calls

Read the plates in an image by URL
Write No write-style endpoint inferred; pick any operation from the API reference. See the full list on the API page.

Query synced data

Synced entities support tenant.platerecognizer.db.<entity>.search() and .list(): usage. See Database for filters and operators.

What’s next

API reference

Every platerecognizer.api.* operation with input and output types.

Database

Synced entities, search filters, and operators.

Connect / OAuth

createLink, Hub delivery, and tenant connect flows.

Use with agents

Expose this plugin’s operations as MCP tools.