- Industry
- Insure AI
- Department
- Engineering
- Team
- Application Engineering
- Kind
- Assistant
- Approver
- Integration Lead
- Code
- ENG-05
It connects the insurer's systems through their APIs: broker and aggregator quote feeds, bancassurance partner integrations, repairer and loss adjuster networks, and the payments and fraud-screening services. It handles retries, rate limits and the protection of policyholder and health data in transit.
How it works
6 steps, and a person signs off before step 6.
- 01Looks it up
Finds the record the request is about in the agent and broker portal: the partner's API contract and data sharing agreement..
- 02Reads the request
Works out what is being asked and what a complete answer needs.
- 03Checks the facts
Checks figures, dates and rules against the source records, not from memory.
- 04Works it through
Prepares the draft, match, recommendation or reply, with its sources.
- 05Asks a person
Hands the work to Integration Lead with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the code repository: it opens the integration change with mapping and tests. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The integration catalogue, partner API contracts, data sharing agreements, the personal and health data rules and retry patterns.
Reads from
the agent and broker portal: the partner's API contract and data sharing agreement.
Acts in
the code repository: it opens the integration change with mapping and tests.
Hands back
An object with mapping (a list, each with source_field, target_field and transform), data_shared (a list), retry_policy, tests and rollout.
Asks a person when
The integration shares personal or health data with a new partner, or moves money.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Most retries | 3 | Then the message goes to the dead-letter queue. |
| Rate limit headroom (%) | 20 | Stay this far below the partner's limit. |
| Send only needed personal data | On | When on, fields not in the data sharing agreement are dropped. |
| Partner sandbox first | On | When on, every integration passes in the partner sandbox first. |
| Dead letters that alert | 10 | Alert at this many in an hour. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- When on is true, send only fields in the data sharing agreement; never send health data to a partner without that agreement.
- Retry at most 3 times and stay 20 percent under rate limits.
- When on is true, pass the partner sandbox before production.
- Alert at 10 dead letters an hour.
- Quotes from aggregators are always re-priced by the rating engine before bind.
See the API Integration Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.