api-exploration

Tests Fusebase API endpoints interactively using temporary tokens before writing application code.

5|2|Updated Feb 9, 2026
One-click install
npx skills add https://github.com/ryan-haver/fusebase-mcp --skill api-exploration-ryan-haver
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: api-exploration
Source: https://github.com/ryan-haver/fusebase-mcp/tree/main/apps/client-portal-dashboard/.claude/skills/api-exploration
Command: npx skills add https://github.com/ryan-haver/fusebase-mcp --skill api-exploration-ryan-haver

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires @fusebase/dashboard-service-sdk.

What problem does it solve? When integrating with the Fusebase API, you often don't know an endpoint's exact behavior, response shape, or schema before writing production code. This Skill provides a repeatable workflow for creating short-lived tokens and running direct test calls so you can verify API behavior first and avoid debugging guesswork inside your app. ## Core Features & Use Cases - Temporary Token Generation: Creates 15-minute tokens via the fusebase token create CLI command scoped to a specific app ID from fusebase.json. - Direct API Testing: Runs throwaway TypeScript scripts (e.g. _test-api.ts) with bun to call endpoints using the x-app-feature-token header and inspect raw responses. - SDK Verification: Validates @fusebase/dashboard-service-sdk calls such as listing databases and reading dashboard rows before wiring them into UI code. - Use Case: Before building a dashboard widget, you run a test script to confirm the CustomDashboardRowsApi.getRows response structure, then implement the real feature with confidence. ## Quick Start Ask the AI to create a temporary Fusebase token and run a test script that calls the API endpoint you want to verify, then inspect the response output.

Frequently Asked Questions about api-exploration

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

FAQPage Schema
How do I test a Fusebase API endpoint before writing app code?▼

Create a temporary token with `fusebase token create --app <appId>`, then write a throwaway TypeScript script that calls the endpoint with the `x-app-feature-token` header and run it with bun. Inspect the status and JSON response, iterate, then implement in your app.

How to verify @fusebase/dashboard-service-sdk calls before using them in UI code?▼

Write a test script that creates a client with the dashboard-service base URL and your temporary token, then call methods like `DatabasesApi.listDatabases` or `CustomDashboardRowsApi.getRows`. Run it with bun and inspect the logged JSON output.

How long does a Fusebase temporary token last?▼

Temporary tokens created with `fusebase token create` expire after 15 minutes. If your token expires during testing, simply create a new one and re-run your script.

Where does the appId come from when creating a Fusebase token?▼

The appId comes from your project's `fusebase.json` configuration file, specifically from the `apps[].id` field. Pass it to the CLI as `fusebase token create --app <appId>`.

Why is my Fusebase API test call failing with authentication errors?▼

Authentication failures usually mean the token expired (15-minute lifetime) or the `x-app-feature-token` header is missing or malformed. Also confirm the base URL host matches your environment's `FUSEBASE_HOST`, such as `app-api.thefusebase.com` for production.