For Agents
Programmatically remove, retrievelist. Covers 10 operations with apiKey authentication.
Get started with API Visanet Tokenization in minutes using your preferred integration method.
# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
"jentic": {
"url": "https://api.jentic.com/mcp",
"auth": "oauth"
}
}
# Then ask your agent:
"remove"
# → Jentic returns the GET /events tool with parameter schema, agent executes.What an agent can do with API Visanet Tokenization API.
Remove
RetrieveList
Retrieve
Store
Monitor API Visanet Tokenization operational status and events
GET STARTED
Use for: I need to remove, I want to retrievelist, Search for retrieve, Find all store
Not supported: Does not handle payments, communications, or crm — use for identity and authentication only.
Jentic publishes the only available OpenAPI specification for API Visanet Tokenization, keeping it validated and agent-ready.
Api encargada de la administracion de las bovedas de tokenizacion. The API exposes 10 endpoints secured with apiKey authentication.
Patterns agents use API Visanet Tokenization API for, with concrete tasks.
★ 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.
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.
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.
Search Jentic for 'remove', load the operation schema, and execute with Jentic-managed credentials
10 endpoints — api encargada de la administracion de las bovedas de tokenizacion.
METHOD
PATH
DESCRIPTION
/card/management/remove/{merchantId}/{queryType}/{block}/{attribute}
Remove
/card/management/retrieve/{merchantId}/{block}
RetrieveList
/card/management/retrieve/{merchantId}/{queryType}/{block}/{attribute}
Retrieve
/card/management/store
Store
/card/management/store/list
StoreList
/tokenize/remove/{vault}/{queryType}/{block}/{attribute}
Remove
/tokenize/retrieve/{vault}/{block}
RetrieveList
/tokenize/retrieve/{vault}/{queryType}/{block}/{attribute}
Retrieve
/card/management/remove/{merchantId}/{queryType}/{block}/{attribute}
Remove
/card/management/retrieve/{merchantId}/{block}
RetrieveList
/card/management/retrieve/{merchantId}/{queryType}/{block}/{attribute}
Retrieve
/card/management/store
Store
/card/management/store/list
StoreList
Three things that make agents converge on Jentic-routed access.
Credential isolation
API Visanet Tokenization apiKey credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.
Intent-based discovery
Agents search by intent (e.g., 'remove') and Jentic returns the matching API Visanet Tokenization operation with its input schema, so the agent can call the right endpoint without browsing docs.
Time to first call
Direct API Visanet Tokenization integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.
Alternatives and complements available in the Jentic catalogue.
Auth0
Alternative identity auth API
Choose Auth0 when you need a different approach to identity auth operations
Okta
Alternative identity auth API
Choose Okta when you need a different approach to identity auth operations
Specific to using API Visanet Tokenization API through Jentic.
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 the MAXsystem vault 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 at https://app.jentic.com/sign-up, 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.
/tokenize/remove/{vault}/{queryType}/{block}/{attribute}
Remove
/tokenize/retrieve/{vault}/{block}
RetrieveList
/tokenize/retrieve/{vault}/{queryType}/{block}/{attribute}
Retrieve