api-integration

Plan and integrate new API data sources into the Super Legal MCP platform.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/Number531/Legal-API --skill api-integration-number531
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: api-integration
Source: https://github.com/Number531/Legal-API/tree/main/.claude/skills/api-integration
Command: npx skills add https://github.com/Number531/Legal-API --skill api-integration-number531

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a structured, repeatable process to plan, implement, and wire a new API data source into the Super Legal MCP platform, reducing time-to-production and ensuring consistency across native, websearch, and hybrid pathways.

Core Features & Use Cases

  • End-to-end API integration workflow: API research, 3-file client creation (native, Exa websearch fallback, hybrid wrapper), 7-file wiring (rate limiter, tool schemas, tool implementations, domain MCP servers, subagent mappings, prompt constants, client registry), frontend catalog updates, testing, and documentation updates.
  • Comprehensive platform wiring: updates to rate limiter maps, tool schemas, domain mappings, bindings, and domain subagent access to new capabilities.
  • Use Case: add a new government/regulatory/financial API to the MCP pipeline and enable agents to query, test, and display results through the catalog.

Quick Start

Follow the guided process to research, implement native, websearch, and hybrid clients, then wire them into the platform and run tests.

Frequently Asked Questions about api-integration

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I integrate a new government or financial API data source into my platform?

API integration involves researching the data source, creating native and websearch fallback clients, and wiring them into your platform's tool schemas, rate limiters, and domain mappings to deliver production-ready regulatory or financial data queries.

What is the process for wiring an API client into a domain MCP server?

Wiring an API client into a domain MCP server requires updating rate limiter maps, tool schemas, tool implementations, subagent mappings, prompt constants, and client registries to ensure agents can successfully query and display the new data source.

How do I set up a hybrid API client with native and websearch fallback?

A hybrid API client combines a native API data source connection with an Exa websearch fallback within a wrapper file, ensuring data retrieval continuity and robust validation when the primary government or financial API endpoint fails.

Do I need to handle rate limiting and environment variables when adding a regulatory API?

Yes, adding a regulatory API requires enforcing environment variable handling for credentials and updating rate limiter maps to prevent exceeding request limits, ensuring the integration delivers robust and production-ready data retrieval.

What's the best way to update a frontend catalog after connecting a new API?

Updating a frontend catalog after connecting a new API involves adding the new data source to the display pipeline, enabling agents to query, test, and display results through the platform interface alongside comprehensive documentation updates.

How does api-integration handle testing for new API data source connections?

The api-integration process includes comprehensive testing and documentation updates as its final step, validating the native, websearch, and hybrid client pathways to ensure the newly wired regulatory or financial API is production-ready.