BridgeFill

The system

BridgeFill is a developer-time integration tool for API providers, consumers, and coding agents. A provider publishes an OpenAPI schema and a working code sample. A consumer can discover that contract and ask for integration files tailored to a language, framework, and use case. The public repository includes an MCP interface, REST API, CLI, and developer dashboard.

Contracts and change

The schema registry keeps version history. Its diff engine classifies breaking, warning, additive, and informational changes, then applies semantic versioning. Conflict checks focus on the endpoints a consumer uses, so an unrelated change need not block that integration. Generated files are validated against the published contract before they are returned.

Implementation

The repository documents a TypeScript server with a memory backend for local development and PostgreSQL persistence as an option. It uses scoped JWTs and API keys for tool access and records audit events. The dashboard is a single HTML page served by the application. The README lists 13 MCP tools and a REST interface for registry, generation, and validation workflows.

Generation and validation

When an LLM key is configured, generation can use a provider's code sample as a grounding example. Without one, the repository documents a deterministic fallback that still generates schema-grounded files. This is a useful boundary: code generation and contract validation are separate steps.

Evidence still to add

The public source and local setup instructions are available. A live hosted deployment, usage figures, and performance measurements have not been independently verified.