IFFCO-Tokio General Insurance

IFFCO‑TOKIO General Insurance Company Limited, incorporated in 2000 as a joint venture between Indian Farmers Fertiliser Co‑operative Limited (IFFCO) and Tokio Marine Group, offers a comprehensive portfolio of general insurance products in India, including motor, health, travel, home, and corporate policies such as property and liability insurance. The company also provides niche solutions like cyber, credit, fine arts, and errors & omissions insurance, and runs rural‑centric initiatives such as Sankat Haran Bima Yojana and Mahila Suraksha Bima Yojana to increase insurance penetration.

IFFCO-Tokio General Insurance is profiled on the APIs.io network. Tagged areas include Insurance, GeneralInsurance, India, JointVenture, and FinancialServices.

IFFCO-Tokio General Insurance’s developer surface includes signup flow, support, engineering blog, and 6 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

14.7/100 emerging Agent 0/100 human only Full breakdown ↓
scored 2026-10-31 · rubric v0.25.0 · Show this score on your site →

0 APIs

InsuranceGeneralInsuranceIndiaJointVentureFinancialServices

Kin Score

Kin Score How this is scored →
scored 2026-10-31 · rubric v0.25.0

Composite quality — 14.7/100 · emerging

Contract Quality 0.0 / 21

Developer Ergonomics 1.2 / 17

Access Clarity 5.8 / 17

Operational Transparency 0.0 / 11

Contract Governance 0.0 / 10

Discoverability 4.1 / 9

Regulatory Posture 4.1 / 15

Agent readiness — 0/100 · human only

Machine-Readable Contract 0 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 0 / 10

Idempotency 0 / 9

Stable Error Semantics 0 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 0 / 7

Typed Event Surface 0 / 6

Agent Skills 0 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 5 / 5

Distinct Operations 3 / 3

Regulatory Posture applies to this provider. Its tags matched the Insurance regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.

The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/iffco-tokio/"><img src="https://apis.io/badge/iffco-tokio/card.svg" alt="IFFCO-Tokio General Insurance on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

Machine-Readable Contract +18 pts — api_specs includes an OpenAPI document
MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship
Agentic Access Contract +10 pts — agentic_access artifact present (x-agentic-access), graded by author
Machine-Readable Auth +10 pts — a served openid-configuration/oauth-authorization-server carrying `issuer` (served), else the securitySchemes class in the provider OpenAPIs — bound (mutualTLS, DPoP, Signature) > negotiable (oauth2 authorizationCode/clientCredentials, openIdConnect) > bearer (http bearer, apiKey)
Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0

13 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Contract Quality scores 0.0 — up to +25.0 composite points
Developer Ergonomics scores 7.1 — up to +18.6 composite points
Access Clarity scores 34.2 — up to +13.2 composite points

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/iffco-tokio/apis.yml: open an issue on github.com/api-evangelist/iffco-tokio to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Iffco Tokio Authentication

0 schemes

SECURITY

Iffco Tokio Domain Security

TLSv1.2 · HSTS · DMARC

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

Iffco Tokio Scopes

OAuth 2.0 · no documented scopes

0 scopes

SCOPES

Resources

Get Started 1

Portal, sign-up, and the first successful call

SignUp

SignUp

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

LLMsTxt

LLMsTxt

Access & Security 1

Authentication, authorization, and security posture

DomainSecurity

DomainSecurity

Operate 1

Status, limits, changes, and where to get help

Support

Support

Commercial 2

Pricing, plans, and the legal terms of use

TermsOfService

TermsOfService

PrivacyPolicy

PrivacyPolicy

Company 2

The organization behind the API

Website

Website

Blog

Blog

Other 1

Properties that don't map to a standard resource type

Hosts

Hosts

Source (apis.yml)

aid: iffco-tokio
name: IFFCO-Tokio General Insurance
description: IFFCO‑TOKIO General Insurance Company Limited, incorporated in 2000 as a joint venture between Indian Farmers
  Fertiliser Co‑operative Limited (IFFCO) and Tokio Marine Group, offers a comprehensive portfolio of general insurance products
  in India, including motor, health, travel, home, and corporate policies such as property and liability insurance. The company
  also provides niche solutions like cyber, credit, fine arts, and errors & omissions insurance, and runs rural‑centric initiatives
  such as Sankat Haran Bima Yojana and Mahila Suraksha Bima Yojana to increase insurance penetration.
image: https://www.iffcotokio.co.in/content/dam/iffcotokio/iffco-images/logo.jpg
url: https://artifacts.apis.io/iffco-tokio/apis.yml
x-type: company
x-source: harvest:new-submission
x-tier: profiled
x-tier-reason: enrichment pass 2026-10-28 (modular-v1; was harvest)
specificationVersion: '0.20'
created: '2026-10-28'
modified: '2026-10-28'
tags:
- Insurance
- GeneralInsurance
- India
- JointVenture
- FinancialServices
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: LLMsTxt
  url: llms/iffco-tokio-llms.txt
- type: Hosts
  url: hosts/iffco-tokio-hosts.yml
- type: TermsOfService
  url: https://www.iffcotokio.co.in/about-us/terms-use
- type: SignUp
  url: https://www.iffcotokio.co.in/claims/register-a-claim
- type: DomainSecurity
  url: security/iffco-tokio-domain-security.yml
- type: Website
  url: https://iffcotokio.co.in/
- type: PrivacyPolicy
  url: https://www.iffcotokio.co.in/about-us/privacy-policy
- type: Support
  url: https://www.iffcotokio.co.in/contact-us
- type: Blog
  url: https://www.iffcotokio.co.in/blog
apis: []
x-submission-probe: 200, 2026-10-26
x-coverage:
  state: unreadable
  reason: no-machine-readable-spec
  detail: The provider's website returns HTML error pages for typical OpenAPI spec URLs and provides no machine‑readable API
    specification.
  evidence:
  - url: https://www.iffcotokio.co.in/openapi.json
    status: 200
  checked: '2026-10-28'
x-enrichment:
  date: '2026-10-28'
  status: enriched
  artifacts_added: 21
  pass: modular-v1
  engine: identity=oss,contract=oss,surfaces=oss,docs=oss,regulatory=oss

IFFCO-Tokio General Insurance API — frequently asked questions

How do I authenticate with the IFFCO-Tokio General Insurance API?

IFFCO-Tokio General Insurance documents its authentication (0 schemes). The details are profiled on APIs.io as Iffco Tokio Authentication.

Is the IFFCO-Tokio General Insurance API ready for AI agents?

IFFCO-Tokio General Insurance has a Kin Score of 14.7 out of 100 (emerging) and an Agent Readiness score of 0.0 (human-only), scored by API Evangelist on 2026-10-31.

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/iffco-tokio"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/iffco-tokio/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/iffco-tokio/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.