canonical: https://jentic.com/apis/agentedigitalkasnet.com/agentedigitalkasnet

# Agentedigitalkasnet QR Interop API - Clientes

The Kasnet QR Interop API lets wallet clients generate and query interoperable payment QR codes across Peru's interbank QR network. It exposes two operations: one to create a QR code for an end user and one to look up the details of an existing code. Requests authenticate with an API key sent in the x-api-key header.

## For AI agents

Generate interoperable payment QR codes for wallet end users and query the status and details of an existing QR code.

## Scope

Does not handle card processing, settlement, or refunds - use for interoperable payment QR generation and lookup only.

## Capabilities

- Generate an interoperable payment QR code for a wallet end user
- Query the details and status of a previously generated QR code
- Authenticate wallet client requests with an issued API key

## Use cases

### Wallet QR code generation

A digital wallet needs to hand its user a scannable code to receive an interoperable payment. The Kasnet QR Interop API creates the QR for the end user so any participating wallet on Peru's interbank network can pay it. The wallet passes its issued API key in the x-api-key header on each call.

Example prompt: Call POST `/clients-interop/generate-qr` with the end user's payment details and return the generated QR payload

### QR status and detail lookup

After issuing a code, a wallet backend needs to confirm its details or current state. The query operation returns the stored information for a given QR so the wallet can reconcile it against a payment or display it back to the user.

Example prompt: Call POST `/clients-interop/query-qr` with the QR reference and return its details for reconciliation

### AI agent payment QR issuance

An AI agent building a checkout flow can issue and verify interoperable QR codes without hand-wiring the Kasnet auth header. Through Jentic the agent discovers the two operations by intent and calls them with the wallet's stored API key.

Example prompt: Search Jentic for 'generate a payment QR code', load the schema, and issue a QR for a checkout total

## Key resources

- **Interoperable QR** — Generate a payment QR code for a wallet end user
- **QR query** — Retrieve the details and status of an existing QR code

## AI readiness

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.

- **Score:** 68 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 100 / 100
  - Developer Experience & Jentic Compatibility: 75 / 100
  - AI-Readiness & Agent Experience: 50 / 100
  - Agent Usability: 94 / 100
  - Security: 50 / 100
  - AI Discoverability: 69 / 100
- **View full report:** https://jentic.com/apis/agentedigitalkasnet.com/agentedigitalkasnet/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring the Kasnet QR Interop API by hand means setting the x-api-key header on every request and shaping the generate and query payloads yourself. Through Jentic you install once, import the API from the API Directory, store your credential once, and your agent calls it.
- **Permission scoping:** The Kasnet QR Interop API takes its inputs in the request body rather than a resource id in the URL path, so you limit the agent to the operations it needs, such as generating a QR code. You credit the agent only with the operations you allow, so querying stays out unless you add it.
- **Credential handling:** Your the Kasnet QR credential 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.
- **Discovery method:** Agents search Jentic by intent such as 'generate a payment QR code', and Jentic returns the matching operation with its input schema so the agent calls the right endpoint without browsing docs.

## Related APIs

- **Stripe API** — Full card and wallet payment processing with a global reach
- **Square API** — In-person and online payments with QR and terminal support
- **Xero Accounting API** — Accounting and invoicing to reconcile the payments you collect

## FAQ

### What authentication does the Kasnet QR Interop API use?

The Kasnet QR Interop API authenticates with an API key passed in the x-api-key header. Kasnet issues the key to the wallet client. Through Jentic the key is stored encrypted in your own instance and injected into each call at run time.

### Is there a the Kasnet QR Interop API MCP server?

You don't need an MCP server to give your agent the Kasnet QR Interop API. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent calls it. That keeps another server's tool definitions out of your agent's context while still giving it the operation set from the spec.

### Which operations does the Kasnet QR Interop API expose?

It exposes two operations: one to generate an interoperable payment QR code for a wallet end user, and one to query the details of an existing QR code. Both are POST requests scoped to the wallet client identified by the API key.

### Can I limit what my agent is allowed to do with the Kasnet QR Interop API?

Yes. Because you run Jentic One yourself, your own rules decide which the Kasnet QR Interop API operations and credentials the agent may use. You grant only the operations it needs, such as generating a QR code, so any operation you have not granted stays off limits unless you add it. The choice of what the agent may call is yours.

### How do I connect my agent to the Kasnet QR Interop API through Jentic?

Search Jentic by intent such as 'generate a payment QR code' to discover the operation, load its input schema, and your agent calls it with your stored credential injected at run time. To run it on your own infrastructure, install Jentic One from its GitHub repo.
