About the index
How Bindex works
Bindex is a neutral directory of insurance APIs and MCP servers. We list, we don't vouch. Every rule below exists to keep those two sentences true.
The unit is a capability, not a company
Each listing is one specific capability — a claims API, an underwriting MCP server, a distribution SDK — offered by a provider. Providers have pages too, but the atomic unit buyers compare is the capability.
Where the data comes from
Every listing carries a source chip: public sources means we compiled it from publicly available information; self-reported means the provider submitted or synced it. When a provider verifies ownership, the teal Claimed chip appears — it means the data comes from them, not that we endorse it.
Freshness is visible, always
Every listing shows when it was last updated, in a monospace chip. Past 30 days the chip turns amber; past 90 it turns red and says stale. We never hide aging data — we label it.
Sort order can never be bought
Results sort by recency, listing completeness, or name — all mechanical, all inspectable. Paid placements (featured slots, sponsorships) are separate, labeled units that never touch search order. See pricing for exactly what is and isn't for sale.
What we don't sell
Rankings, badges of quality, verification, reviews, your data. Not at any price. The full charter is at /neutrality, and the listing rules at /legal/listing-policy.
Keeping listings current
Claimed providers edit in the portal or sync programmatically via the listing sync API. Every write stamps the freshness chip — buyers always see the honest date.
How “Similar listings” are picked
The Similar listings block on every capability page is a fixed formula scored against all other providers' capabilities — no click data, no machine learning, no randomization, and nothing a vendor can buy. The exact points:
- +3 — shared value-chain stage (any overlap)
- +2 — per shared line of business, capped at +4
- +2 — country overlap (or both Global); otherwise +1 for region overlap — geography contributes at most +2
- +1 — shared consumption mode (API, MCP or SDK — any overlap)
A listing needs a score of at least 4 to appear; if fewer than two qualify, the block is hidden entirely. Ties break by most recently updated, then alphabetically. Claimed status, plan tier, featured status and listing completeness are excluded from the formula by design — and by test. Records from the same provider never appear here; they live in the separate “More from” block instead.