Veem Global Payments API

Setup

Wiring the Veem Global Payments API by hand means handling its bearer JWT auth, choosing between the sandbox and production veem.com hosts, and coding each account, bank account, and payment operation yourself. Through Jentic you install once, import the Veem Global Payments API from the API Directory, store the token once, and your agent calls it.

Permission scoping

Veem puts the account and bank account ids in the URL path (/account/{accountId}, /account/bank-account/{bankAccountId}), so a rule can pin your agent to one account. You choose the operations it may call, so money-moving ones like creating a claimless payment are not included unless you add them.

Credential isolation

Your Veem bearer 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.

Intent-based discovery

Agents search Jentic by intent such as 'create a claimless payment' or 'add a bank account', and Jentic returns the matching Veem operation with its input schema so the agent calls the right endpoint without browsing the reference docs.