external_apis

Proxy external API requests through Replit-managed billing and parse result.body.

Updated Feb 9, 2026
One-click install
npx skills add https://github.com/soq123/SE3354-Calo-fit --skill external-apis-soq123
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: external_apis
Source: https://github.com/soq123/SE3354-Calo-fit/tree/main/.local/skills/external_apis
Command: npx skills add https://github.com/soq123/SE3354-Calo-fit --skill external-apis-soq123

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Accessing external APIs often requires managing credentials and billing across multiple services. This skill provides a single, safe way to route requests through Replit-managed billing, reducing credential exposure and simplifying usage.

Core Features & Use Cases

  • Proxy requests to external APIs via a centralized, billed gateway.
  • Use the Brave connector example to retrieve real web image results for analysis and rendering.
  • Integrate with code_execution to invoke externalApi__<connector_name> using a path, method, and query, then parse result.body for downstream workflows.

Quick Start

Call externalApi__<connector_name> from code_execution with a path, method, and query to fetch data via the Replit-managed billing proxy.

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 calls with managed billing in code execution workflows?

You can proxy external API calls with managed billing by invoking externalApi__<connector_name> from code_execution using a path, method, and query, routing requests through a Replit-managed billing gateway to reduce credential exposure.

What problem does a centralized API proxy gateway solve when accessing external services?

A centralized API proxy gateway solves the problem of managing credentials and billing across multiple external services by providing a single, safe route through Replit-managed billing, simplifying usage and reducing credential exposure.

How do I retrieve web image results using the Brave connector through an API proxy?

To retrieve web image results using the Brave connector, call externalApi__brave from code_execution with the appropriate path, method, and query parameters, then parse result.body for the downstream media URLs and assets.

Do I need to manage my own credentials when proxying requests to external connectors?

You do not need to manage your own credentials when proxying requests to external connectors, because the Replit-managed billing proxy securely handles credentials and applies passthrough billing for the proxied API calls.

How do I parse external API responses for downstream workflows after using a proxy?

You parse external API responses for downstream workflows by extracting data from result.body returned by the externalApi__<connector_name> call, including media assets and URLs, directly within your code_execution environment.

Are there limitations when using a Replit-managed proxy for external API requests?

The Replit-managed proxy for external API requests requires using code_execution workflows and supports specific connector integrations by invoking externalApi__<connector_name> with a path, method, and query, limiting usage to available connectors.