1K+ reviewsDevelopers & AI builders
Connect the MCP server and your assistant creates tracked links and QR codes, builds the journey behind them, and reads back who scanned what. REST and SDKs in five languages if you would rather call it yourself.
One command to connect an assistant
TypeScript, Python, Go, Java, Rust
Scan events pushed to your stack
Use cases
Describe the flow and it creates the link, the QR, the conditions and the destinations. The steps are real workflow objects, not a prompt that has to be re-run.
Generate one per customer, order or asset from your own code, each carrying its own analytics, without minting a new integration every time.
Query who scanned what, where and when over the API, or have events pushed to a webhook as they happen.
Serve links on your own domain so the infrastructure reads as yours, which matters if you are reselling it inside your own product.
FAQ
Create and update links and QR codes, build and connect workflow steps, apply themes, and read analytics and visitor data. The same operations the REST API exposes.
Yes. There is a REST API, SDKs for TypeScript, Python, Go, Java and Rust, a CLI, and Zapier and Make integrations.
Yes. Bring your own domain and links resolve on it. Agencies and platforms run client-facing infrastructure this way.
Self-serve plans cover normal volumes. For high-volume or reseller use, contact [email protected].
