external_apis

Proxy external API requests through Replit-managed passthrough billing.

Updated Apr 6, 2026
One-click install
npx skills add https://github.com/Soufianouassif/Web3-Presale-Platform --skill external-apis-soufianouassif
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: external_apis
Source: https://github.com/Soufianouassif/Web3-Presale-Platform/tree/main/.local/skills/external_apis
Command: npx skills add https://github.com/Soufianouassif/Web3-Presale-Platform --skill external-apis-soufianouassif

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Access to external APIs is made safe and scalable by routing requests through Replit-managed passthrough billing, simplifying credential management and usage tracking.

Core Features & Use Cases

  • Unified API access via connector-based calls like externalApi__<connector_name>, enabling centralized billing and monitoring.
  • Support for URL parameters via query, parsing result.body, and handling media assets through attached_assets when needed.
  • Use Case: fetch real web images from Brave or other services to power chat, analytics, or reports with proper billing and audit.

Quick Start

Call externalApi__brave with a query to fetch Brave image results and process the returned items.

Frequently Asked Questions about external_apis

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

FAQPage Schema
How do I proxy external API requests with managed billing?▼

Proxy external API requests with managed billing by routing them through Replit-managed passthrough billing using a connector-based interface. You call externalApi__<connector_name> with query parameters and parse result.body for structured data.

How does passthrough billing work for external API calls?▼

Passthrough billing works by routing external API requests through Replit-managed infrastructure, which simplifies credential management and tracks API usage centrally. This allows safe and scalable access without managing individual provider accounts.

How do I fetch real web images from Brave using an API proxy?▼

Fetch real web images from Brave by calling externalApi__brave with a query parameter to retrieve image results. You parse the returned items in result.body and save any required media assets under the attached_assets directory.

Do I need to manage my own API credentials for external web requests?▼

You do not need to manage your own API credentials for external web requests when using this proxy. The connector-based interface relies on managed credentials for authentication, abstracting away the need for manual key entry.

What is the best way to handle media assets returned from external APIs?▼

The best way to handle media assets returned from external APIs is to save them under the attached_assets directory. This ensures proper billing and auditing when returning media references for chat, analytics, or reports.

Can I use a connector-based interface for centralized API monitoring?▼

Yes, you can use a connector-based interface for centralized API monitoring. Unified API access via connector calls enables centralized billing and usage tracking while routing requests through a managed passthrough.