external_apis

Proxy external API calls with managed credentials and billing.

Updated Apr 3, 2026
One-click install
npx skills add https://github.com/gopforever/Idle-Echoes --skill external-apis-gopforever
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: external_apis
Source: https://github.com/gopforever/Idle-Echoes/tree/main/.local/skills/external_apis
Command: npx skills add https://github.com/gopforever/Idle-Echoes --skill external-apis-gopforever

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Access external APIs via a secure passthrough proxy with Replit-managed billing to simplify credential handling and cost control.

Core Features & Use Cases

  • Proxied API access with automatic credential management and billing.
  • Simple, connector-based usage to fetch data from external services via externalApi__<connector_name>.
  • Use Brave example to search real web images and render assets through the chat workflow.

Quick Start

Ask the AI to route a request through the external API proxy to fetch data while using the managed credentials.

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 without exposing credentials in my code?

A managed billing proxy handles external API access by routing requests through a secure passthrough. It automatically manages credentials and applies billing controls without exposing keys in your code.

How do I manage API billing and credentials on Replit?

Replit-managed billing controls API costs by routing requests through a secure proxy. This prevents exposing keys in code and simplifies credential management for external services.

Can I fetch real web images using an API connector in a chat workflow?

Yes, you can fetch and render real web images in a chat workflow using an API connector like the Brave example. The proxy returns results dynamically for downstream processing.

Do I need to manually pass API keys when using an external API proxy?

You do not need to manually pass API keys when using this external API proxy. Automatic credential management secures authentication behind the scenes without code exposure.

What is the best way to pass query parameters through an API connector?

The best way to pass query parameters is using the externalApi__<connector_name> interface. This connector format supports parameters and exposes fetched results for downstream processing.