Qrx Codes QRX API
79
AI ReadinessAI-Ready (A-)79/100
Official vendor OpenAPI document · agent-readyMediaImage Processingbearer, apiKey6 EndpointsREST
For Agents
Create picture QR codes from a text prompt and a destination link or Wi-Fi network, wait for or poll the finished image, re-point link codes, and check the account's daily allowance and rate limits.
Use for: Make a QR code that looks like a lighthouse at sunset and opens our menu, Create a Wi-Fi QR code for the cafe network, Check whether my QR code has finished generating, Change where the printed QR code points
Not supported: Does not track scan analytics, shorten arbitrary links, or print materials. Use for generating and re-pointing prompt-painted QR codes only.
The QRX API makes picture QR codes: you send a prompt describing what the image should show plus a destination link, or Wi-Fi details on the Starter plan, and QRX paints a scannable code in that scene. Codes are made asynchronously, so creation returns an id, a shortUrl, and a processing status at once, and the wait parameter can hold the request open until the image is ready. Link codes can be re-pointed after printing, and the account endpoint reports the plan, codes left today, and rate limits.
Install Jentic One Beta
Connect the QRX API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the QRX API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fqrx.codes%2Fqrx" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fqrx.codes%2Fqrx" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with QRX API.
Create a picture QR code from a prompt and a destination URL, optionally in a style from the styles list
Create a Wi-Fi QR code with ssid, password, and wpa or wep security on the Starter plan
Wait up to 50 seconds for a code to finish with the wait parameter instead of polling
Send an Idempotency-Key so a retried create cannot produce a second code
Re-point a link code's destination after printing so scans follow at once
Check the plan, remainingToday, resetsAt, and rateLimits on the account
Use Cases
Patterns agents use QRX API for, with concrete tasks.
★ Agent-made picture QR codes through Jentic
A design or marketing agent produces on-brand QR art for a campaign: it lists styles, creates a code from a prompt and destination with an Idempotency-Key, and waits for the image. Through Jentic the qrx_live_ key is injected by the developer's own Jentic One instance, so the agent never holds it.
GET /v1/styles, then POST /v1/codes?wait=45 with prompt 'A lighthouse on a cliff at sunset', destination 'https://example.com/menu', and an Idempotency-Key header
Branded Wi-Fi codes for venues
Cafes and hotels print Wi-Fi codes on table cards. On the Starter plan, a create request with a wifi object of ssid, password, and security produces a code that joins the network, painted in a scene that matches the venue.
POST /v1/codes with prompt 'A cosy coffee shop counter' and wifi {ssid 'CafeGuest', password 'latte2026', security 'wpa'}
Re-pointing printed codes
PATCH /v1/codes/{id} changes a link code's destination on the Starter plan, and printed codes follow at once, so a poster can move from a launch page to an order page without reprinting.
PATCH /v1/codes/{id} with destination 'https://example.com/new-menu'
Allowance-aware batch creation
Every API code counts against the plan's daily allowance. GET /v1/account returns dailyLimit, remainingToday, resetsAt, and the rateLimits object, so an agent can pace a batch and stop before the allowance runs out.
GET /v1/account, read codes.remainingToday, and create at most that many codes with POST /v1/codes
Key Endpoints
6 endpoints — the qrx api makes picture qr codes: you send a prompt describing what the image should show plus a destination link, or wi-fi details on the starter plan, and qrx paints a scannable code in that scene.
METHOD
PATH
DESCRIPTION
POST
/v1/codes
Create a code
GET
/v1/codes/{id}
Get a code's status and image
PATCH
/v1/codes/{id}
Change where a code points
GET
/v1/codes
List codes
GET
/v1/styles
List styles
GET
/v1/account
Get the account
POST
/v1/codes
Create a code
GET
/v1/codes/{id}
Get a code's status and image
PATCH
/v1/codes/{id}
Change where a code points
GET
/v1/codes
List codes
GET
/v1/styles
List styles
GET
/v1/account
Get the account
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
Q
QRX API
- AI-Ready (A-)79/100
93
Foundational Compliance74
Developer Experience & Jentic Compatibility86
AI-Readiness & Agent Experience94
Agent Usability55
Security69
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.2
Show dimension breakdown
93
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A+Signals: 4
99%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
100%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
75%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
74
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: A-Signals: 4
21%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
75%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
86
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: ASignals: 4
72%
Description Coverage
Coverage of descriptions across API elements.
100%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
100%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
71%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
55
Security
Trust, risk posture, and security compliance.
Grade: CSignals: 1
55%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
69
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: B+Signals: 1
69%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring QRX by hand means choosing between its bearer and X-API-Key header forms, generating Idempotency-Key values for safe retries, and handling the asynchronous create with wait or polling yourself. Through Jentic you install once, import QRX from the API Directory, store the key once, and your agent calls it.
Permission scoping
QRX puts the code id in the URL path (/v1/codes/{id}), so a rule can pin your agent to one code: it can read or re-point that code and nothing else. You choose the operations it may call, so re-pointing printed codes is not included unless you add it.
Credential isolation
Your QRX key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'create a picture QR code' or 'check codes left today', and Jentic returns the matching QRX operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using QRX API through Jentic.
What authentication does the QRX API use?
The QRX API declares two schemes for the same API key: bearerAuth, sending the qrx_live_ key as an Authorization bearer token (preferred), and apiKeyHeader, sending it in an X-API-Key header for clients that cannot set an authorisation scheme. Through Jentic the key is stored encrypted by your own Jentic One instance and injected at execution time.
How do I know when a QRX code is ready?
Creation is asynchronous: POST /v1/codes answers 202 with the code processing. Pass wait (up to 50) to hold the request open until it finishes, or call GET /v1/codes/{id} with wait to get the status and, once it has succeeded, the image.
What are the rate limits for the QRX API?
The OpenAPI spec does not publish fixed numbers; GET /v1/account returns your live rateLimits, each with a limit and windowSeconds, plus the daily code allowance in dailyLimit and remainingToday. See https://qrx.codes/developers/docs for details.
How do I create a picture QR code with QRX through Jentic?
Install Jentic One, import the QRX API from the Jentic API Directory, and store your qrx_live_ key. Your agent searches for 'create a picture QR code', Jentic returns POST /v1/codes with its schema, and the agent calls it with a prompt and destination. To run it on your own infrastructure, install Jentic One from its GitHub repo.
Is there a QRX MCP server?
You don't need an MCP server to give your agent QRX. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent calls it, discovering operations on demand rather than loading every tool definition into its context.
Can I limit what my agent is allowed to do with the QRX API?
Yes. Write a rule that allows only POST /v1/codes, GET /v1/codes/{id}, and GET /v1/styles, so the agent can create new codes and fetch them while re-pointing existing printed codes stays out of reach. Every call it makes is logged.
GET STARTED