external_apis

Proxy external API requests through Replit-managed billing without exposing credentials.

Updated Mar 20, 2026
One-click install
npx skills add https://github.com/ItsJupiter000/hot-outreach --skill external-apis-itsjupiter000
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: external_apis
Source: https://github.com/ItsJupiter000/hot-outreach/tree/main/.local/skills/external_apis
Command: npx skills add https://github.com/ItsJupiter000/hot-outreach --skill external-apis-itsjupiter000

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Access to external APIs through Replit-managed billing to safely proxy requests and manage credentials.

Core Features & Use Cases

  • Proxied API access via Replit-managed billing for supported connectors.
  • Use the externalApi__<connector_name> interface from code_execution to fetch data without exposing credentials.
  • Retrieve and render results like images or data for applications needing live web information.

Quick Start

Retrieve real web data by calling the Brave API via the externalApi__brave connector and process results in your code.

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 through Replit billing?

To proxy external API requests through Replit billing, use the externalApi__<connector_name> interface within code_execution to fetch live web data without exposing credentials.

How does Replit-managed billing handle API credentials safely?

Replit-managed billing handles API credentials safely by routing proxied web requests internally, allowing you to retrieve data and images without exposing secrets in your code.

Can I use the Brave API connector to fetch live web data in code?

Yes, you can use the externalApi__brave connector to fetch live web data and process results directly in your code execution environment.

Do I need to manage authentication keys to access supported external APIs?

No, you do not need to manage authentication keys manually; the external_apis interface handles safe credential management for supported connectors via Replit billing.

What are the limitations of routing external web requests through Replit billing?

Routing external web requests through Replit billing is limited to supported connectors, restricting proxied API access to those specific data sources and image rendering options.

What's the best way to retrieve real web data without exposing secrets?

The best way to retrieve real web data without exposing secrets is using Replit-managed billing to proxy requests, presenting results like images or data without credential exposure.