external_apis

Proxy external API requests through Replit-managed passthrough billing.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/CRAJKUMARSINGH/M3_Bridge --skill external-apis-crajkumarsingh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: external_apis
Source: https://github.com/CRAJKUMARSINGH/M3_Bridge/tree/main/.local/skills/external_apis
Command: npx skills add https://github.com/CRAJKUMARSINGH/M3_Bridge --skill external-apis-crajkumarsingh

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Access external APIs securely by routing requests through Replit-managed passthrough billing, reducing credential handling and simplifying usage tracking.

Core Features & Use Cases

  • Proxy external API calls through a managed billing channel to simplify authentication and governance.
  • Use the externalApi__<connector_name> invocation from code_execution to interact with specific services and parse result.body.
  • Save media or large results under attached_assets for rendering in chat or UI, as demonstrated by Brave image results.

Quick Start

Call externalApi__brave with a search query to fetch image results and integrate the returned URLs into your UI.

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

To proxy external API calls, use the externalApi__<connector_name> invocation from code execution to route requests through Replit-managed passthrough billing, which handles authorization and simplifies usage tracking.

How do I save media assets from API results for display in chat?

Save media assets from API results by storing them under attached_assets, which allows you to render large results or media like Brave image URLs directly in your chat or UI.

What is passthrough billing for external API connectors?

Passthrough billing is a managed authorization mechanism that securely routes external API requests, reducing the need to handle credentials manually while tracking usage through the Replit platform.

How do I pass URL parameters when proxying external APIs?

When proxying external APIs, you pass URL parameters by using a query within the externalApi__<connector_name> invocation from code execution, then parse the returned result body.

Does this external API proxy approach work with Brave image search?

Yes, this approach works with Brave image search by calling externalApi__brave with a search query to fetch image results and integrating the returned URLs into your user interface.

Why should I use managed billing instead of handling API credentials directly?

Using managed billing instead of handling credentials directly reduces credential handling overhead, applies secure access governance, and simplifies usage tracking for external API connectors.