Can I generate QR codes for WiFi or contact cards with LinQR?

Yes. POST /qrcode/wifi accepts SSID, password, and security type. POST /qrcode/contact accepts vCard-style fields (name, phone, email). Both return image bytes ready to print, no client-side composition needed.

What are the request size and timeout limits for the LinQR API?

Maximum request size is 32MB and request timeout is fixed at 180 seconds. These limits matter most for /batch/qrcode jobs and for /images uploads when embedding large brand logos in codes.

How do I generate a branded QR code through Jentic?

Run pip install jentic, then upload a brand image once via POST /images. Search Jentic for 'generate a branded QR code', load the POST /qrcode schema, supply the image id with the QR payload, and execute. The returned image bytes can be saved or inlined directly.

Can LinQR produce QR codes in bulk?

Yes. POST /batch/qrcode accepts an array of payloads in one call and returns the generated images together, which avoids per-item HTTP overhead. Keep total request size under 32MB and the job under 180 seconds - split very large catalogues into multiple batches.

Can I limit what my agent is allowed to do with the LinQR API?

Yes. Because you self-host Jentic One, your own rules decide which LinQR operations and credentials the agent may use, so you can allow only the generation calls it needs, such as POST /qrcode or POST /qrcode/wifi, and leave everything else out. LinQR takes the QR content in the request body rather than a resource id in the URL path, so scoping is done per operation rather than per record. Image management such as DELETE on uploaded brand images stays unavailable to the agent unless you explicitly add it. The stored client secret or RapidAPI key is injected only at execution time and never reaches the agent's prompt or logs.