Developers

Insurance intelligence, your way. REST, CLI, MCP, or agents.

Whether you're integrating via REST API, connecting through Model Context Protocol, or building autonomous agent workflows, Carpe meets your engineering team where they are.

JSON APIs for production workflows

MCP and ACP-ready for AI-native architecture

Enterprise integration patterns for carrier systems

Developer experience showing Carpe API documentation, code, and workflow tooling

Integration modes

Bring Carpe into the stack you already run, or the one you're building next.

From enterprise integration teams to AI-native builders, Carpe exposes insurance intelligence in the form that makes adoption easiest.

REST API

Production-grade REST endpoints for entity enrichment, claims intelligence, and underwriting data. Batch and real-time. JSON in, structured intelligence out.

MCP Server

Connect Carpe as a Model Context Protocol server. Your AI agents get direct access to insurance intelligence, entity lookups, risk signals, claims context, as native tool calls.

CLI Tools

Ship faster with `carpe-cli`. Query entities, run enrichment jobs, and pipe results into your existing data pipelines from the command line.

Agent Frameworks

Build autonomous insurance workflows with LangChain, CrewAI, AutoGen, or any ACP-compliant agent. Carpe provides the tools, context, and structured output agents need.

Code examples

From enrichment calls to agent tool invocations.

The same intelligence foundation can power Python services, TypeScript copilots, and command-line workflows without forcing your team into one integration pattern.

Python

# Python — Entity Enrichment
from carpe import CarpeClient

client = CarpeClient(api_key="your-key")
result = client.enrich(
    entity="Meridian Construction LLC",
    modules=["business", "web", "risk"]
)
print(result.risk_summary)

Legacy or next-gen

We meet your architecture where it is, and where it’s going.

Some teams are wiring Carpe into long-standing carrier systems. Others are designing agent workflows from scratch. Both should work.

Enterprise integration

Guidewire, Duck Creek, Unqork, ClaimSearch, and the rest of the real world.

Batch files, webhooks, SFTP, and system-to-system APIs still matter. Carpe fits into your current carrier stack and makes it smarter without forcing a rip-and-replace motion.

Your existing stack, enhanced with Carpe intelligence.

AI-native architecture

MCP servers, ACP compliance, agent tool calls, and streaming responses.

Build with Model Context Protocol, wire Carpe into autonomous workflows, and let your agents consume structured insurance-grade signal as native tools instead of screen-scraped glue.

Your AI agents, powered by insurance-grade signal.

Security & compliance

Built for enterprise review, not just developer excitement.

Insurance engineering teams still need governance, defensibility, and deployment discipline. Carpe is designed to support technical evaluation and enterprise scrutiny at the same time.

Encryption in transit and at rest for production deployments
Reviewable outputs designed for carrier governance and audit scrutiny
Access controls, data handling policies, and deployment patterns aligned to enterprise security review
Flexible delivery models for hosted workflows, APIs, and controlled integration into existing systems

Start building with insurance intelligence.

Talk with Carpe about APIs, implementation patterns, MCP access, or the fastest path from proof-of-value to production workflow.