# Fintary

> AI-powered commission management and revenue operations platform for insurance
> distribution — brokerages, carriers and wealth firms. Automates compensation calculation
> across hierarchies, splits, overrides and bonuses; reconciles carrier statement data;
> tracks chargebacks and advances; surfaces revenue and profitability analytics; and runs a
> white-label producer portal. Fintary publishes two OpenAPI 3.0.0 contracts on its own API
> host at api.fintary.com. Both require credentials issued through a Fintary representative
> against an existing customer tenant — there is no self-service signup and no published
> pricing.

Generated by API Evangelist from the catalog profile at
https://github.com/api-evangelist/fintary. Fintary does not publish an llms.txt of its own;
https://fintary.com/llms.txt returns HTTP 404. Nothing here is a claim by Fintary.

## APIs

- [Fintary Open API](https://api.fintary.com/openapi-doc): 21 operations under `/openapi/`.
  Agents (list, create, get, update), uplines (assign, remove), an agent's commissions,
  payouts, policies and dashboard snapshot, analytics reports/datasets/widgets, commission
  report data, document upload and HTML-to-PDF conversion. Auth: `x-api-key` header or HTTP
  bearer.
- [Fintary AMS API](https://api.fintary.com/api-doc): 60 operations under `/api/ams/`.
  Policies (detail, status, team, tasks, commission, document repository), customers, agents,
  agent contracts, hierarchy and full upline/downline tree, tasks and escalation, custom-field
  and status configuration, and a page-config/capabilities registry. Auth: HTTP bearer.

Base URL for both: `https://api.fintary.com`

## Specs

- [Fintary Open API OpenAPI 3.0.0](https://raw.githubusercontent.com/api-evangelist/fintary/refs/heads/main/openapi/fintary-open-api-openapi.yml)
- [Fintary AMS API OpenAPI 3.0.0](https://raw.githubusercontent.com/api-evangelist/fintary/refs/heads/main/openapi/fintary-ams-api-openapi.yml)
- [Verbatim harvested Open API JSON](https://raw.githubusercontent.com/api-evangelist/fintary/refs/heads/main/openapi/_original/fintary-open-api-openapi.json)
- [Verbatim harvested AMS API JSON](https://raw.githubusercontent.com/api-evangelist/fintary/refs/heads/main/openapi/_original/fintary-ams-api-openapi.json)

Neither spec is served at a standalone `.json` or `.yaml` URL. Both are embedded in the
`__NEXT_DATA__` of the server-rendered documentation pages, which is why a conventional
`/openapi.json` probe against every Fintary host returns 404.

## Docs

- [Documentation (SSO integration guides)](https://api.fintary.com/documentation)
- [Open API reference](https://api.fintary.com/openapi-doc)
- [AMS API reference](https://api.fintary.com/api-doc)
- [Product](https://www.fintary.com/product)
- [Carriers](https://www.fintary.com/carriers)
- [Resources](https://fintary.com/resources)
- [Glossary](https://www.fintary.com/glossary/main)
- [Contact / support](https://www.fintary.com/contact-us)
- [Application login](https://app.fintary.com)
- [Status page](https://fintary.instatus.com/)

## Derived artifacts

- [Authentication profile](https://raw.githubusercontent.com/api-evangelist/fintary/refs/heads/main/authentication/fintary-authentication.yml)
- [API conventions](https://raw.githubusercontent.com/api-evangelist/fintary/refs/heads/main/conventions/fintary-conventions.yml)
- [Error catalog](https://raw.githubusercontent.com/api-evangelist/fintary/refs/heads/main/errors/fintary-problem-types.yml)
- [Data model](https://raw.githubusercontent.com/api-evangelist/fintary/refs/heads/main/data-model/fintary-data-model.yml)
- [Lifecycle](https://raw.githubusercontent.com/api-evangelist/fintary/refs/heads/main/lifecycle/fintary-lifecycle.yml)
- [Conformance](https://raw.githubusercontent.com/api-evangelist/fintary/refs/heads/main/conformance/fintary-conformance.yml)
- [Rate limits](https://raw.githubusercontent.com/api-evangelist/fintary/refs/heads/main/rate-limits/fintary-rate-limits.yml)
- [Plans and pricing](https://raw.githubusercontent.com/api-evangelist/fintary/refs/heads/main/plans/fintary-plans-pricing.yml)
- [Agent skills](https://raw.githubusercontent.com/api-evangelist/fintary/refs/heads/main/skills/_index.yml)

## What an agent should know before calling

- Every call needs a credential. There is no anonymous, sandbox or test surface, and no
  self-service key issuance — credentials come from a Fintary representative.
- Send `x-api-key: <key>` to the Open API, or `Authorization: Bearer <token>` to either API.
- Neither API is idempotent. No `Idempotency-Key` header exists, so a retried POST to
  `/openapi/agents`, `/api/ams/policies`, `/api/ams/customers` or `/api/ams/tasks` can create
  a duplicate record.
- There is no rate-limit signal. No 429 is declared on any of the 81 operations and no
  `RateLimit-*` or `Retry-After` header is returned, so back-off must be self-imposed.
- Four different error envelopes are in play: `{error, code}`, `{error}`, `{code, message}`
  and — observed live but described by no schema — `{success, data, message, statusCode}`.
  Parse defensively.
- The AMS document declares no operationIds; refer to its operations by method and path.
- Records are keyed by a string `strId` / `str_id`. Integer report IDs still work on the
  analytics routes but the spec marks them deprecated.
- Pagination is 0-based `page` plus `limit` or `page_size` on the Open API; the AMS list
  routes paginate inside a POST body.
- Large analytics exports should use `csv_output=true&background_task=true` and then poll
  `GET /openapi/analytics/tasks/{taskId}`.
- There is no event surface. No webhooks, no AsyncAPI, no MCP server and no agent card —
  polling is the only option.