api-contract-tester

Verify live API endpoints against documented contracts and generate pass/fail test reports.

11|1|Updated Mar 3, 2026
One-click install
npx skills add https://github.com/ylxmf2005/AgentCorp --skill api-contract-tester-ylxmf2005
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: api-contract-tester
Source: https://github.com/ylxmf2005/AgentCorp/tree/main/agentcorp/api-contract-tester
Command: npx skills add https://github.com/ylxmf2005/AgentCorp --skill api-contract-tester-ylxmf2005

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Real-world API contracts can be difficult to prove without running against the actual service; this skill provides hands-on verification to ensure live endpoints conform to their promised contract.

Core Features & Use Cases

  • Runtime contract verification against HTTP, JSON-RPC, and other exposed interfaces.
  • Collects evidence from real requests/responses, status codes, and auth boundaries to support compliance and migration decisions.
  • Use Case: When a API change is proposed, verify compatibility before rollout and generate a test report with pass/fail details.

Quick Start

Run a live-contract test against the target API to confirm it honors the documented contract.

Frequently Asked Questions about api-contract-tester

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

FAQPage Schema
How do I verify that my live API endpoints honor their documented contracts?

API contract verification is performed by executing tests against the live service, capturing real requests and responses to confirm endpoints conform to their promised behavior.

Can I run runtime contract testing for both HTTP and JSON-RPC interfaces?

Runtime contract testing supports HTTP, JSON-RPC, A2A, and CLI surfaces, allowing you to verify exposed interfaces where runtime compliance is required.

How do I test API compatibility before rolling out a proposed change?

To test API compatibility before rollout, execute live-contract tests against the target service to generate a test-result artifact with pass/fail evidence.

Does contract testing work by mocking services or sending real requests?

Contract testing works by sending real requests to the live target, capturing actual responses, status codes, and auth boundaries as evidence rather than relying on mocks.

What is the best way to collect evidence for API migration decisions?

The best way to collect evidence for API migration is to execute runtime contract verification, capturing real request and response data to support compliance decisions.

When should I not use runtime contract verification for my API?

Runtime contract verification should not be used when you cannot execute against real targets, as it requires a live service to capture requests, responses, and status codes for pass/fail evidence.