Infile Sa API-SIGNER-CERTIFICADORES

Setup

Wiring the API-SIGNER-CERTIFICADORES by hand means implementing its JWT bearer flow, calling get_token to obtain a token, attaching it to the certificar request, and handling refresh and retries yourself. Through Jentic you install once, import API-SIGNER-CERTIFICADORES from the API Directory, store the credential once, and your agent calls it.

Permission scoping

The certification targets travel in the request body, not the URL path, so you limit the agent to the operations it needs, such as requesting a token and certifying. Only the operations you add are in the allowed set, so the agent's reach stays your own positive choice.

Credential isolation

Your API-SIGNER-CERTIFICADORES bearer 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.

Intent-based discovery

Agents search Jentic by intent such as 'get a signing token if the credentials are valid', and Jentic returns the matching API-SIGNER-CERTIFICADORES operation with its input schema so the agent calls the right endpoint without browsing the reference docs.