slot-rpc

Configure Cartridge RPC endpoints with bearer token authentication and CORS whitelisting.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/Kepler22bee/House-of-Stark --skill slot-rpc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: slot-rpc
Source: https://github.com/Kepler22bee/House-of-Stark/tree/main/contracts/.agents/skills/slot-rpc
Command: npx skills add https://github.com/Kepler22bee/House-of-Stark --skill slot-rpc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams securely configure Cartridge's Starknet RPC endpoints by enabling API token authentication, managing domain CORS whitelists for browser clients, and providing log inspection tools for operational visibility.

Core Features & Use Cases

  • Authenticated RPC access: Use bearer API tokens to protect server-to-server RPC calls to Cartridge endpoints.
  • Browser-friendly CORS whitelisting: Add root domains (including subdomains) to allow direct browser calls without exposing tokens, with IP-based rate limits.
  • Token and whitelist management: Create, list, and delete tokens and whitelist entries via CLI, and view paginated logs with time filters.
  • Use Case: Allow a frontend on a whitelisted domain to call the Sepolia RPC endpoint while backend services use team-scoped API tokens for secure transactions.

Quick Start

Configure Cartridge RPC tokens and add your frontend's domain to the whitelist for team my-team.

Frequently Asked Questions about slot-rpc

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

FAQPage Schema
How do I configure API token authentication for Starknet RPC endpoints?

API token authentication for Starknet RPC endpoints is configured using bearer tokens to protect server-to-server calls. You can create, list, and delete these tokens via CLI to manage secure access to Cartridge's mainnet and sepolia networks.

Can I whitelist browser domains for CORS access to Sepolia RPC without exposing API tokens?

Yes, you can whitelist root domains for CORS access to Sepolia RPC to allow direct browser calls without exposing tokens. Adding a root domain automatically includes its subdomains, and IP-based rate limiting is applied for security.

What is the best way to manage Cartridge RPC token lifecycles and domain whitelists?

The best way to manage Cartridge RPC token lifecycles and domain whitelists is via CLI commands. This allows you to create, list, and delete API tokens and CORS whitelist entries for both server-side and browser clients.

How do I query RPC logs with time filters and pagination for operational visibility?

You can query RPC logs with time filters and pagination to gain operational visibility. This feature allows you to inspect log entries by applying duration filters and paginating through results to monitor endpoint activity.

Does Cartridge RPC support both server-side bearer tokens and browser-based CORS whitelisting?

Yes, Cartridge RPC supports both server-side bearer tokens and browser-based CORS whitelisting. Backend services use team-scoped API tokens for transactions, while frontend apps on whitelisted domains make direct browser calls.

Why are my subdomains blocked from making browser calls to the Starknet RPC endpoint?

Subdomains may be blocked if the root domain is not properly added to the CORS whitelist. Configuring a root domain in the whitelist automatically includes its subdomains, enabling direct browser calls to the RPC endpoint.