canonical: https://jentic.com/apis/swaggerhub.visanetperu/api-visanet-tokenization

# Visanetperu API Visanet Tokenization

API encargada de la administracion de las bovedas de tokenizacion. The API exposes 10 endpoints secured with apiKey authentication.

## For AI agents

Programmatically remove, retrievelist. Covers 10 operations with apiKey authentication.

## Scope

Does not handle payments, communications, or crm - use for identity and authentication only.

## Capabilities

- Remove
- RetrieveList
- Retrieve
- Store
- Monitor API Visanet Tokenization operational status and events

## Use cases

### Identity and Authentication Operations

Use the API Visanet Tokenization to perform identity auth operations programmatically. The API provides 10 endpoints covering core functionality including remove, retrievelist, retrieve.

Example prompt: Call POST /card/management/remove/{merchantId}/{queryType}/{block}/{attribute} to remove

### Automated Tokenization Management

Automate tokenization operations by combining multiple API Visanet Tokenization endpoints. Agents can retrievelist and then retrieve in a single workflow.

Example prompt: Call GET /card/management/retrieve/{merchantId}/{block} to retrievelist, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call API Visanet Tokenization endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey tokens manually.

Example prompt: Search Jentic for 'remove', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | /card/management/remove/{merchantId}/{queryType}/{block}/{attribute} | Remove |
| GET | /card/management/retrieve/{merchantId}/{block} | RetrieveList |
| GET | /card/management/retrieve/{merchantId}/{queryType}/{block}/{attribute} | Retrieve |
| POST | /card/management/store | Store |
| POST | /card/management/store/list | StoreList |
| POST | /tokenize/remove/{vault}/{queryType}/{block}/{attribute} | Remove |
| GET | /tokenize/retrieve/{vault}/{block} | RetrieveList |
| GET | /tokenize/retrieve/{vault}/{queryType}/{block}/{attribute} | Retrieve |

## Key resources

- **Tokenization** — RESTful API to manage tokenization.

## Why Jentic

- **Setup:** Wiring API Visanet Tokenization by hand means obtaining an access token from api.security, sending it in the Authorization header, and constructing the merchant, vault, block, and attribute path segments correctly on every card management call. Through Jentic you install once, import API Visanet Tokenization from the API Directory, store the access token once, and your agent calls it.
- **Permission scoping:** API Visanet Tokenization puts the merchant and vault ids in the URL path (/card/management/retrieve/{merchantId}/{block} and /tokenize/retrieve/{vault}/{block}), so a rule can pin your agent to one merchant or vault. You choose the operations it may call, so destructive ones like card removal or token removal are not included unless you add them.
- **Credential handling:** Your API Visanet Tokenization access token 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 'tokenize a card' or 'retrieve a stored card', and Jentic returns the matching API Visanet Tokenization operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Auth0** — Alternative identity auth API
- **Okta** — Alternative identity auth API

## FAQ

### What authentication does the API Visanet Tokenization use?

The API Visanet Tokenization uses an API key passed in the `Authorization` header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I remove with the API Visanet Tokenization?

Yes. Use the POST /card/management/remove/{merchantId}/{queryType}/{block}/{attribute} endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the API Visanet Tokenization?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I remove through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'remove'. Jentic returns the matching API Visanet Tokenization operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the API Visanet Tokenization have?

The API Visanet Tokenization exposes 10 endpoints covering tokenization operations.

### Can I limit what my agent is allowed to do with the API Visanet Tokenization?

Yes. Because you run Jentic One yourself, your own rules decide which API Visanet Tokenization operations and credentials the agent may use. You can allow read calls like GET /card/management/retrieve/{merchantId}/{block} and GET /tokenize/retrieve/{vault}/{block} while leaving destructive operations such as card removal (POST /card/management/remove) and token removal (POST /tokenize/remove) out of scope. Since the merchant and vault ids sit in the URL path, a rule can also pin the agent to a single merchant or vault.