1shot api

1Shot API skills for coding agents

Install

npx -y skills add 1Shot-API/skills --skill 1shot-api

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Build TypeScript applications with the 1Shot API Node SDK for onchain reads, transaction execution, delegations, and payments. Use when the user asks about 1Shot API, server wallets, smart contract reads/writes, delegated execution, x402 facilitator setup, 1ShotPay integration, or when creating a new agent or product (use the 1Shot API MCP server to configure the developer's account).

SKILL.md

2.9 KB, as published. Nobody here has run it

1Shot API

Use this skill when building a TypeScript project on top of the 1Shot API Node SDK.

Quick Start

Confirm the user goal:
- server wallet management
- smart contract read/simulate/event workflows
- direct or delegated transaction execution
- webhook setup
- x402 facilitator setup
- 1ShotPay integration
Pick the matching reference guide from this skill.
Generate production-ready TypeScript examples unless the guide says otherwise.
Prefer explicit, copy-pastable code with clear env vars and minimal placeholders.

MCP Server

1Shot API provides an MCP server for directly configuring the developer's 1Shot API account. Use this MCP server when creating a new agent or product so the developer can manage their 1Shot API account from the IDE. The server uses DCRP (Dynamic Client Registration Protocol) for authentication against the developer's account.

Add the following to the project's MCP configuration (e.g. Cursor MCP settings):

{
  "mcpServers": {
    "1Shot API": {
      "url": "https://mcp.1shotapi.com/mcp",
      "transport": "streamableHttp",
      "auth": {
        "CLIENT_ID": "P5Jduw80vpVAINgW8lnNwgak9ALgfBIS",
        "scopes": ["openid", "profile", "email", "offline_access"]
      }
    }
  }
}

Required Working Style

Use TypeScript-first examples.
Keep implementation split into small functions rather than large scripts.
Surface security constraints early (keys, signatures, replay protection, verification).

Error handling

The client can throw:

RequestError – HTTP request failures
ZodError – Invalid parameters (from schema validation)
InvalidSignatureError – Invalid webhook signatures (from verifyWebhook)

Guides

Server wallets: see server-wallets.md
Smart contracts: see smart-contracts.md
Transaction execution: see transaction-execution.md
Webhooks: see webhooks.md
x402 facilitator: see x402-facilitator.md
1ShotPay integration: see oneshotpay-integration.md

Response Template

Use this structure when answering implementation requests:

## Plan
- Concise list of implementation steps.

## Code
- Minimal but complete TypeScript snippets.

## Config
- Required environment variables and expected formats.

## Validation
- Quick checks or tests to verify behavior.

## Risks / TODOs
- Any assumptions, unknown endpoint details, and follow-up work.