Codes from your own systems
Create codes, repoint them and read scan figures over HTTP. Scoped, revocable tokens; published rate limits; every call attributable to the token that made it.
AI assistants, over MCP
The same API, exposed as a Model Context Protocol server at https://lynkarr.com/mcp. Connect Claude or another assistant with an API token and it can list your codes, create them, change where an existing one points, and read the scan analytics — in a sentence, rather than through four screens.
Every tool is a call to this API, so the token's scopes, the rate limit and the monthly quota apply exactly as they do to a script. An assistant given a read-only token is not shown the tools that would write, so it cannot try and fail.
What it is for
Anything where the codes are a consequence of something else happening — a product being created, an order being packed, a property being listed. Generating those by hand is where a QR programme stops scaling.
Tokens
Created and revoked in the app, scoped to what they need, and shown once. A revoked token stops working immediately rather than at the end of some cache window.
The documentation is public
Read it before you buy. Finding out whether the integration you need is possible should not require a sales call.
API access is part of the Enterprise plan.
See it happen
What you can do with it
For when the codes are a consequence of something else
A product being created, an order being packed, a property being listed. Generating those by hand is exactly where a QR programme stops scaling, and it is the point at which people usually give up on the idea.
Tokens that are scoped, revocable and attributable
Created and revoked in the app, scoped to what they need, shown once. A revoked token stops working immediately rather than at the end of some cache window, and every call is attributable to the token that made it.
Read the figures back out
Scans and conversions by code, so your own systems can hold the numbers rather than somebody having to export a spreadsheet every Monday.
Getting there
-
Read the documentation
It is public. Find out it fits before you talk to anybody.
-
Create a token
Scoped to what your integration actually needs.
-
Create codes from your system
At the moment the thing they describe is created.
-
Read the figures back
Into whatever you already use for reporting.
More in the same place
Questions
Which plan includes it?
API access is part of Enterprise.
Can I see the docs before buying?
Yes — they are public. Finding out whether an integration is possible should not require a sales call.
What are the rate limits?
Published in the documentation rather than discovered in production, which is the only way a limit is any use when you are designing against it.
Try it with one code
The free plan has no expiry and asks for no card, and the analytics behind it are the same ones a paying customer gets.
Free forever for one person. No card, and 10,000 scans a month included.