What authentication does the Eversend API use?

Per its OpenAPI spec, the Eversend API uses a JWT bearer token. You exchange your clientId and clientSecret at the token endpoint to obtain the token, then send it as a bearer token on subsequent calls. Through Jentic the credential is stored encrypted by your own instance and injected at call time, so it never reaches the agent.

Is there an Eversend MCP server?

You don't need an MCP server to give your agent Eversend. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent calls operations like creating a payout quotation or executing a payout on demand, without loading another server's tool definitions into its context.

Can I limit what my agent is allowed to do with Eversend?

Yes. Write a rule that allows only the quotation and read operations, for example creating a payout quotation and listing transactions, so the agent can price and monitor transfers but cannot execute a payout, exchange, or terminate a card unless you add those operations. Because Eversend puts wallet and card ids in the URL path, read access can also be pinned to a specific wallet or card, and every call the agent makes is logged.

Can I send mobile money payouts with the Eversend API?

Yes. First fetch the delivery countries and the delivery banks for a country, then create a payout quotation to lock the rate and fees, and execute the payout against a mobile money wallet or bank account. You can read the resulting transaction to confirm its status.

What are the rate limits for the Eversend API?

The OpenAPI spec does not specify rate limits. Check the Eversend developer documentation at https://eversend.readme.io for current limits before running high-volume payout or collection jobs.

How do I create a payout with the Eversend API through Jentic?

Search Jentic for 'send a mobile money payout', which returns the payout quotation and payout operations with their input schemas. The agent creates a quotation for the amount and destination, executes the payout, and reads the transaction to confirm settlement, with your stored credential injected at call time.