Skip to main content
skillsFirst-partyReview first Safety Privacy

REST API Client Harness Skill

Explore and script against REST APIs with comprehensive authentication support (API keys, OAuth 2.0, JWT Bearer tokens, Basic Auth), pagination utilities (cursor-based, offset-based, page-based), retry logic with exponential backoff and jitter, error handling for HTTP status codes, rate limiting with Retry-After hea...

HarnessClaude CodeCodexWindsurfGeminiCursorCLI
Level:advancedType:generalVerified:draft
Review first review before installing

Open the source and read safety notes before installing.

Citation facts

Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.

Source URLs
https://developer.mozilla.org/en-US/docs/Web/HTTP/Guides/Overview, https://github.com/JSONbored/awesome-claude/blob/main/content/skills/rest-api-client-harness.mdx
Package URL
/downloads/skills/rest-api-client-harness.zip
Package SHA256
7ca26f7e32710870302ff983bbd1f2b443b756a67af553ece30441be5e3b329c
Safety notes
Setup downloads/unzips a package, and the harness makes live HTTP requests (including POST/PUT/DELETE) to the APIs you point it at; review endpoints and methods before running against production services.
Privacy notes
API requests carry credentials (API keys, OAuth/JWT tokens) and request/response bodies; keep secrets in environment variables, and review what data is sent to and logged from third-party APIs.
Platform compatibility
claude-code (native-skill), codex (native-skill), windsurf (native-skill), gemini (native-skill), cursor (adapter), cli (manual-context)
Author
JSONbored
Claim status
unclaimed
Last verified
2025-10-15

Decision playbook

Ready to evaluate for your workflow

Signals are comparatively strong, but you should still validate source, privacy posture, and package provenance for your environment.

Compare context
Selected

0

Current score

96

Baseline

Delta

No baseline selected

No major trust-signal divergence detected in the current selection.

Source and provenance checks

Complete

Confirm ownership and provenance before trusting install instructions.

  • Source link availableRequired

    Open the canonical repository and verify ownership.

    Done
  • Source provenance statusRequired

    Marked as first-party.

    Done
  • Metadata reviewed

    Registry metadata indicates a reviewed listing.

    Done

Safety and privacy checks

Complete

Validate risk disclosures before installation or API wiring.

  • Safety notes presentRequired

    Review the listed safety guidance before running commands.

    Done
  • Privacy notes presentRequired

    Review data handling notes before connecting accounts or secrets.

    Done
  • Trust level risk gateRequired

    Trust level does not block evaluation.

    Done

Package and install checks

Complete

Check package metadata and artifact integrity signals.

  • Install payload available

    Install or copy payload is available for review.

    Done
  • Package verification flag

    Package marked verified.

    Done
  • Checksum metadata

    SHA-256 hash is present.

    Done

Compare-driven decision checks

Needs review

Use compare context to validate trade-offs before adoption.

  • Compare tray has multiple entries

    Add at least one more entry to compare trust differences.

    Pending
  • Baseline comparison available

    No baseline peer selected yet.

    Pending
  • Diverging trust signals identified

    No major trust-signal divergence found.

    Pending

Setup at a glance

Package install

Copy-ready — paste the snippet to get started.

Install command

Provided

Config snippet

Not provided

Copy snippet

Provided

Prerequisites

6 to clear

Platforms

6 listed

Difficulty

100/100

Adoption plan

Balanced adoption plan

Current risk score 0/100. Use staged verification before broader rollout.

Risk 0

Pre-adoption checks

Validate source and review signals before any execution.

  • Confirm source provenanceRequired

    Source URL/provenance metadata is present.

    Done
  • Confirm metadata review state

    Listing has review metadata.

    Done
  • Verify install payload

    Install/config payload exists and can be inspected.

    Done

Security checks

Confirm safety, privacy, and package integrity signals.

  • Review safety notesRequired

    Safety notes are present.

    Done
  • Review privacy notesRequired

    Privacy notes are present.

    Done
  • Verify package integrity metadata

    Package verification/checksum metadata is available.

    Done

Rollout

Adopt in controlled steps based on the selected plan.

  • Run in isolated sandbox firstRequired

    Use a constrained sandbox and observe behavior across multiple tasks.

    Pending
  • Roll out graduallyRequired

    Roll out to a small cohort before wider usage.

    Pending
  • Set monitoring and fallback

    Define rollback path and monitor errors after adoption.

    Pending

Evidence readiness

Evidence readiness matrix · balanced

Required evidence gates are covered (6/6 signals complete).

Risk 0

Source provenance

Present

Source repository/provenance is listed.

Required in this preset

Metadata review

Present

Review metadata is present.

Required in this preset

Safety notes

Present

Safety notes are present.

Required in this preset

Privacy notes

Present

Privacy notes are present.

Optional in this preset

Package integrity

Present

Package integrity metadata is present.

Optional in this preset

Install payload

Present

Install payload is available.

Required in this preset

Required evidence gates are covered for this preset.

Decision timeline

Decision timeline · balanced

6/6 steps complete with no blocking gaps for this preset.

Risk 0

triage

Confirm source provenanceRequired

Source/provenance metadata is available.

Done

triage

Check metadata review statusRequired

Review metadata is available.

Done

verify

Review safety notesRequired

Safety notes are available.

Done

verify

Review privacy notes

Privacy notes are available.

Done

verify

Validate package integrity metadata

Package integrity metadata is available.

Done

rollout

Verify install payload and commandsRequired

Install payload is available.

Done

No required blockers for this timeline preset.

Prerequisite readiness

Prerequisite readiness

6 prerequisites to line up before setup. Have accounts and credentials ready first.

0/6 ready
Account & credentials1Install & runtime3Network & hosting2

Safety & privacy surface

Safety & privacy surface

1 safety and 1 privacy notes across 2 risk areas. Review closely: credentials & tokens, network access.

2 areas
  • SafetyNetwork accessSetup downloads/unzips a package, and the harness makes live HTTP requests (including POST/PUT/DELETE) to the APIs you point it at; review endpoints and methods before running against production services.
  • PrivacyCredentials & tokensAPI requests carry credentials (API keys, OAuth/JWT tokens) and request/response bodies; keep secrets in environment variables, and review what data is sent to and logged from third-party APIs.

Safety notes

  • Setup downloads/unzips a package, and the harness makes live HTTP requests (including POST/PUT/DELETE) to the APIs you point it at; review endpoints and methods before running against production services.

Privacy notes

  • API requests carry credentials (API keys, OAuth/JWT tokens) and request/response bodies; keep secrets in environment variables, and review what data is sent to and logged from third-party APIs.

Prerequisites

  • Node.js 18+
  • undici or axios HTTP client library
  • API credentials (if required)
  • Network access for API requests
  • Network access to target API endpoints for making HTTP requests and testing API functionality
  • API documentation or OpenAPI/Swagger specification (optional but recommended) for automatic client generation and type safety

Schema details

Install type
package
Reading time
6 min
Difficulty score
100
Troubleshooting
Yes
Breaking changes
No
Package metadata
Package verified
Yes
SHA-256
7ca26f7e32710870302ff983bbd1f2b443b756a67af553ece30441be5e3b329c
Skill and platform metadata
Skill type
general
Skill level
advanced
Verification
draft
Verified at
2025-10-15
Retrieval sources
https://developer.mozilla.org/en-US/docs/Web/HTTP/Overview
Tested platforms
ClaudeCodexOpenClawCursorWindsurfGemini
PlatformSupportInstall path
claude-codeNative.claude/skills/<skill-name>/SKILL.md
codexNative.agents/skills/<skill-name>/SKILL.md
windsurfNative.windsurf/skills/<skill-name>/SKILL.md
geminiNative.gemini/skills/<skill-name>/SKILL.md or .agents/skills/<skill-name>/SKILL.md
cursorAdapter.cursor/rules/<skill-name>.mdc
cliManualAGENTS.md or tool-specific context file
Full copyable content
import { setTimeout as delay } from 'node:timers/promises';
import { fetch } from 'undici';

async function fetchAll(url, token) {
  let next = url;
  const items = [];
  while (next) {
    const res = await fetch(next, { headers: { Authorization: `Bearer ${token}` } });
    if (!res.ok) {
      if (res.status >= 500) { await delay(1000); continue; }
      throw new Error(`HTTP ${res.status}`);
    }
    const data = await res.json();
    items.push(...data.items);
    next = data.next;
  }
  return items;
}

About this resource

What This Skill Enables

Claude can interact with REST APIs: make requests, handle authentication (API keys, OAuth, JWT), paginate through results, handle rate limits with retries, and process responses. Build API integration scripts, test endpoints, and extract data from web services.

Compatibility

Native

  • Claude Code / Claude: native skill usage via SKILL.md.
  • Codex/OpenAI workflows: compatible with Agent Skills-style SKILL.md content as reusable workflow instructions.

Manual Adaptation

  • Gemini CLI: native skill usage via .gemini/skills/<skill-name>/SKILL.md or .agents/skills/<skill-name>/SKILL.md where supported.
  • Cursor: use the generated .cursor/rules/*.mdc adapter for project rules.
  • OpenClaw and similar agents: use the same skill content as a reusable prompt/workflow file when native skill import is unavailable.

Prerequisites

Required:

  • Claude Pro subscription
  • Code Interpreter feature enabled
  • API credentials (if required by the API)

What Claude handles:

  • Installing HTTP libraries (requests, axios, fetch)
  • Making authenticated requests
  • Handling pagination
  • Retry logic with exponential backoff
  • Response parsing and data extraction
  • Error handling

How to Use This Skill

Simple API Request

Prompt: "Fetch data from this REST API endpoint: https://api.example.com/users Use API key: [your-key] Show me the first 10 results."

Claude will:

  1. Make GET request with auth header
  2. Parse JSON response
  3. Extract and display data
  4. Handle errors gracefully

Paginated Data Extraction

Prompt: "Fetch all pages from this paginated API: URL: https://api.example.com/items Pagination: cursor-based (next_cursor field) API Key: [your-key] Save all results to items.json"

Claude will:

  1. Make first request
  2. Loop through pages using cursor
  3. Collect all results
  4. Save to JSON file
  5. Report total count

POST Request with Data

Prompt: "Create a new user via POST request: URL: https://api.example.com/users Payload: {name: 'John Doe', email: 'john@example.com'} Auth: Bearer token [your-token] Show me the response."

Claude will:

  1. Prepare POST request
  2. Set headers (auth, content-type)
  3. Send JSON payload
  4. Parse response
  5. Display result or error

Batch Operations

Prompt: "Upload all these records to the API:

  • Read from users.csv
  • For each row, POST to /users endpoint
  • Handle rate limits (max 10 requests/second)
  • Log successes and failures
  • Retry failures once"

Claude will:

  1. Read CSV data
  2. Iterate through rows
  3. Make POST requests with rate limiting
  4. Retry on failures
  5. Generate success/failure report

Common Workflows

API Testing & Exploration

"Test this API endpoint:
1. Make GET request to /api/products
2. Check status code and headers
3. Validate JSON response schema
4. Show sample of first 3 records
5. Report if any fields are null/missing"

Data Migration

"Migrate data from API A to API B:
1. Fetch all records from source API (paginated)
2. Transform to target API format
3. POST to destination API
4. Handle rate limits (5 req/sec)
5. Log migration progress and errors
Save unmigrated records to errors.json"

Webhook Testing

"Test this webhook:
1. POST sample payload to webhook URL
2. Check response status
3. Validate response format
4. Test with invalid payload
5. Report all results"

API Monitoring

"Monitor API health:
1. Hit /health endpoint every minute for 10 minutes
2. Record response time and status
3. Alert if response time > 1 second
4. Create uptime report
5. Plot response times"

Authentication Methods

API Key Authentication

  • Header: X-API-Key: your-key
  • Query parameter: ?api_key=your-key
  • Custom header format

Bearer Token (JWT)

  • Header: Authorization: Bearer your-token
  • Token refresh handling
  • Expiration detection

Basic Authentication

  • Header: Authorization: Basic base64(user:pass)
  • Credentials encoding

OAuth 2.0

  • Client credentials flow
  • Authorization code flow
  • Token refresh logic

Advanced Features

Rate Limiting & Retries

  • Respect rate limit headers
  • Exponential backoff
  • Jitter for retry timing
  • Max retry attempts

Response Handling

  • JSON parsing
  • XML/HTML parsing
  • Binary data (images, files)
  • Streaming responses

Error Handling

  • HTTP status code detection
  • Custom error messages
  • Validation errors
  • Network timeouts

Data Transformation

  • JSON to CSV conversion
  • Field mapping and renaming
  • Data type coercion
  • Filtering and aggregation

Tips for Best Results

  1. Provide API Docs: Share API documentation link or describe endpoints
  2. Authentication: Be clear about auth method and provide credentials securely
  3. Rate Limits: Mention any known rate limits ("max 100 requests/minute")
  4. Pagination: Describe pagination style (cursor, offset, page-based)
  5. Error Handling: Specify how to handle failures ("retry 3 times then skip")
  6. Data Volume: Estimate how many requests ("expect 1000 records across 10 pages")
  7. Response Format: Mention expected format (JSON, XML, etc.)

Common Patterns

Cursor-Based Pagination

url = "https://api.example.com/items"
all_items = []
cursor = None
while True:
    params = {"cursor": cursor} if cursor else {}
    response = requests.get(url, params=params)
    data = response.json()
    all_items.extend(data["items"])
    cursor = data.get("next_cursor")
    if not cursor:
        break

Retry with Exponential Backoff

import time
max_retries = 3
for attempt in range(max_retries):
    try:
        response = requests.get(url)
        response.raise_for_status()
        break
    except requests.exceptions.RequestException:
        if attempt < max_retries - 1:
            wait = 2 ** attempt  # 1s, 2s, 4s
            time.sleep(wait)
        else:
            raise

Troubleshooting

Issue: Authentication failing Solution: Double-check auth method and credentials. Show Claude the API docs for auth section.

Issue: Rate limit errors (429) Solution: "Add retry logic with exponential backoff" or "Reduce concurrent requests to 5/second"

Issue: Response parsing errors Solution: "Show me raw response first" then describe expected structure

Issue: Pagination not working Solution: Clarify pagination method: "Use offset pagination starting at 0, increment by 100"

Issue: Timeouts on large requests Solution: "Increase timeout to 60 seconds" or "Fetch in smaller batches"

Issue: CORS errors (in browser context) Solution: Note: Code Interpreter runs server-side, no CORS issues

Learn More

Features

  • Token management patterns (API keys, OAuth 2.0, JWT Bearer tokens, Basic Auth)
  • Pagination utilities (cursor-based, offset-based, page-based pagination)
  • Retry with exponential backoff and jitter for rate limits and transient errors
  • Typed responses (TypeScript) with request/response type safety
  • Rate limiting with Retry-After header support and request throttling
  • Error handling for HTTP status codes, network timeouts, and validation errors
  • Response parsing (JSON, XML, HTML, binary data) with streaming support
  • Batch operations with concurrent request management and progress tracking

Use Cases

  • ETL from third-party APIs with data transformation and validation
  • Backfills and migrations with pagination and error recovery
  • Monitoring scripts with health checks and uptime tracking
  • API testing and exploration with schema validation
  • Webhook testing and validation with payload verification
  • Data synchronization between multiple APIs with conflict resolution

Source citations

Add this badge to your README

Show that REST API Client Harness Skill is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.

Listed on HeyClaude
[![Listed on HeyClaude](https://heyclau.de/badge/skills/rest-api-client-harness.svg)](https://heyclau.de/entry/skills/rest-api-client-harness)

How it compares

REST API Client Harness Skill side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.

3 trust signals differ across this comparison (Package trust, Source provenance, Submitter).

Next steps differ across entries — use the actions in the table below to copy install commands and source links per resource.

Field

Explore and script against REST APIs with comprehensive authentication support (API keys, OAuth 2.0, JWT Bearer tokens, Basic Auth), pagination utilities (cursor-based, offset-based, page-based), retry logic with exponential backoff and jitter, error handling for HTTP status codes, rate limiting with Retry-After hea...

Open dossier

Compile Rust, C++, or Go to WebAssembly and run it in the browser, Node.js, and serverless runtimes: wasm-bindgen JS interop, WASI for system access, the Component Model, and SIMD.

Open dossier

Official Flutter team Agent Skills for AI coding agents building Flutter apps, fixing layout issues, adding widget and integration tests, creating widget previews, applying layered architecture, routing, localization, JSON serialization, and HTTP workflows.

Open dossier

Expert MCP remote server trust review capability pack for auditing OAuth flows, transport security, tool permissions, data exfiltration risk, and vendor scope before connecting Claude Code to third-party MCP servers.

Open dossier
Next stepsDiffers
Trust
Review statusReviewedMaintainer reviewedReviewedMaintainer reviewedReviewedMaintainer reviewedReviewedMaintainer reviewed
Package trustDiffersPackage verified2025-10-15Package verified2025-10-16Package not verifiedPackage not verified
Source provenanceDiffersSource-backedNo submission linkSource-backedSubmission linkedSource submission
SubmitterDifferskiannidev
Install riskReview firstLow riskReview firstReview first
Notes Safety Privacy Safety Privacy Safety Privacy Safety Privacy
Brand
Categoryskillsskillsskillsskills
Sourcefirst-partyfirst-partysource-backedsource-backed
AuthorJSONboredJSONboredFlutter Teamkiannidev
Added2025-10-152025-10-162026-06-182026-06-14
Platforms
Claude CodeCodexWindsurfGeminiCursorCLI
Claude CodeCodexWindsurfGeminiCursorCLI
Claude CodeCodexWindsurfGeminiCursorCLI
Claude CodeCodexWindsurfGeminiCursorCLI
Source repo
Safety notesSetup downloads/unzips a package, and the harness makes live HTTP requests (including POST/PUT/DELETE) to the APIs you point it at; review endpoints and methods before running against production services.The install step downloads and unzips a package, and building modules runs compiler toolchains (wasm-pack, Emscripten, or the WASI SDK); run them in a trusted project directory and review generated build files. WASI grants modules system access (files, env, sockets); grant only the capabilities a module needs and review WASI imports before running untrusted modules.Flutter skills can modify application code, tests, pubspec dependencies, routing, localization files, serialization code, architecture boundaries, and app entry points. Integration-test workflows may enable Flutter Driver extensions, add keys to widgets, launch apps through MCP tools, interact with running UI, and create driver scripts. Do not run device, emulator, browser, Firebase Test Lab, or network-backed integration tests against production services without explicit approval and test credentials. Architecture and routing changes can alter navigation, state management, API access, caching, offline behavior, and user-visible app flows. Use project-local conventions and Flutter version constraints before applying generated examples.Remote MCP servers run outside Anthropic control; Claude Code MCP integration does not guarantee vendor security or data isolation. OAuth tokens issued to an MCP server may grant persistent access to third-party accounts until revoked in the vendor admin console. Tools that read, write, delete, or execute on external systems can cause irreversible production changes when invoked by the model. SSE and streamable HTTP transports must use TLS; do not approve cleartext remote endpoints on untrusted networks. This skill recommends scoping and approval steps; it must not add MCP servers or approve OAuth consent without explicit user authorization.
Privacy notesAPI requests carry credentials (API keys, OAuth/JWT tokens) and request/response bodies; keep secrets in environment variables, and review what data is sent to and logged from third-party APIs.Compiling and running modules is local, but a module that fetches remote models or data (for example ONNX inference) sends and receives data over the network; review what it downloads and where results go.Flutter projects may contain API URLs, Firebase project IDs, mobile bundle IDs, analytics keys, user fixtures, screenshots, test traces, device logs, crash output, and integration-test artifacts. MCP app exploration can expose widget trees, screen text, test data, typed inputs, navigation paths, and screenshots from the running app. HTTP, JSON, localization, and repository-layer work may touch private API schemas, user data models, translations, product copy, and backend payloads. Keep credentials, private endpoints, screenshots with user data, device logs, Firebase tokens, and proprietary UI flows out of public prompts, issues, PRs, and examples.MCP tool results can contain customer names, ticket contents, database rows, repository secrets, and internal URLs that should not be pasted into public issues. OAuth consent screens and server logs may expose account emails, organization identifiers, and access tokens if shared without redaction. Remote server vendors may retain prompts, tool arguments, and responses under their own privacy policies outside Anthropic data handling. Public trust-review summaries should describe risk categories and mitigations, not full tool schemas or live OAuth tokens.
Prerequisites
  • Node.js 18+
  • undici or axios HTTP client library
  • API credentials (if required)
  • Network access for API requests
  • Rust 1.70+ and wasm-pack (recommended)
  • wasm-bindgen 0.2.87+
  • WASI SDK 20+ (for WASI modules)
  • Node.js 18+ for JavaScript integration
  • Flutter SDK and Dart tooling installed for the target project.
  • An AI coding assistant or skill host compatible with Agent Skills, preferably using the standard `.agents/skills` install target.
  • Project-specific Flutter targets, devices, emulators, browsers, test commands, and package constraints available before modifying app code.
  • For MCP-assisted testing or UI exploration, access to the Dart/Flutter MCP server or equivalent app interaction tools.
  • The remote MCP server URL, vendor documentation, and intended Claude Code or Desktop use case.
  • Access to the MCP server manifest, tool list, OAuth client registration details, and transport configuration.
  • Security or platform stakeholders available to review third-party data access before production rollout.
  • A concrete integration goal such as issue tracking, CRM lookup, database queries, or deployment automation.
Install
curl -L https://heyclau.de/downloads/skills/rest-api-client-harness.zip -o rest-api-client-harness.zip && unzip -o rest-api-client-harness.zip -d ./rest-api-client-harness
cargo install wasm-pack
npx skills add flutter/skills --skill '*' --agent universal --yes
Config
Citations
ClaimUnclaimedUnclaimedUnclaimedUnclaimed
Open 4 picks in the interactive comparison tool

Related guides

Signals

Loading live community signals…

More like this, weekly

A short, calm digest of reviewed Claude resources. Unsubscribe any time.