Setup

Wiring the Beneficiary Movement Service API by hand means running Unimed's OAuth 2.0 client credentials exchange, picking among the sandbox and homologation gateway hosts, and refreshing the token yourself. Through Jentic you install once, import Beneficiary Movement Service API from the API Directory, store the client credentials once, and your agent calls it.

Permission scoping

This API puts the beneficiary card number in the URL path (/beneficiarios/{carteirinha}), so a rule can pin your agent to one beneficiary. You choose the operations it may call, so state-changing ones like updating or removing a beneficiary are not included unless you add them.

Credential isolation

Your Unimed client credentials are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'enroll a new beneficiary' or 'update a beneficiary record', and Jentic returns the matching Beneficiary Movement Service API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.