Orthogonal API Platform - Access paid APIs using the SDK, Run API, or x402 direct payment. Search, discover, and integrate APIs with simple tool calls.

v1.0.0

Orthogonal API Platform - Access 100+ premium APIs using the SDK, Run API, or x402 direct payment. Search, discover, and integrate APIs with simple tool calls.

0· 1k·0 current·0 all-time

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for christianpickettcode/orthogonal.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Orthogonal API Platform - Access paid APIs using the SDK, Run API, or x402 direct payment. Search, discover, and integrate APIs with simple tool calls." (christianpickettcode/orthogonal) from ClawHub.
Skill page: https://clawhub.ai/christianpickettcode/orthogonal
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Canonical install target

openclaw skills install christianpickettcode/orthogonal

ClawHub CLI

Package manager switcher

npx clawhub@latest install orthogonal
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Suspicious
high confidence
Purpose & Capability
Name/description and the runtime instructions are consistent: this is an API-discovery and call-integration helper for the Orthogonal platform. The APIs, endpoints, SDK usage, and payment modes in SKILL.md align with the described purpose.
!
Instruction Scope
SKILL.md instructs the agent/user to use ORTHOGONAL_API_KEY and optionally PRIVATE_KEY (for x402 direct payments). The declared registry metadata lists no required environment variables or credentials, creating a mismatch. The instructions also recommend installing @orth/sdk and using fetch-with-payment wrappers that require a raw private key in process.env — this is sensitive and not explicitly declared in the skill manifest.
Install Mechanism
This is an instruction-only skill with no install spec or code files in the bundle. That reduces on-disk risk. However the instructions advise npm install @orth/sdk or using x402 client libraries; installing these third-party packages carries normal supply-chain risk which the skill does not document or pin.
!
Credentials
The skill's runtime instructions clearly require ORTHOGONAL_API_KEY and, for x402 payments, a PRIVATE_KEY environment variable — both are sensitive. The registry metadata, however, lists no required env vars or primary credential, so the manifest underreports the sensitive access the skill expects. Requesting a blockchain private key (even via env) is high sensitivity and should be explicitly declared and justified.
Persistence & Privilege
The skill is not always-enabled, is user-invocable, and allows normal model invocation (defaults). It does not request extra persistence or modify other skills' configuration in the provided materials.
What to consider before installing
This skill appears to be a coherent API marketplace client, but the published metadata does NOT declare the environment variables the instructions require. Before enabling or using it: - Confirm required credentials: the SKILL.md requires ORTHOGONAL_API_KEY and (optionally) a PRIVATE_KEY for direct x402 payments. Ask the publisher to update the manifest to declare these explicitly. - Treat PRIVATE_KEY as highly sensitive: avoid storing long-term private keys in plaintext env vars on shared systems. Prefer ephemeral keys/accounts, restricted wallets with minimal funds, or using a signing service/connector rather than exporting raw private keys into the environment. - Verify the SDK/package: if you plan to npm install @orth/sdk or x402 client libs, verify the package name, author, and integrity (checksums, repository, and official docs) before installing. - Confirm billing implications: the run endpoint charges credits/USDC; make sure you understand pricing and limits and monitor for unexpected charges. - If you need least privilege: create a dedicated API key with limited scope and a separate low-value blockchain account for payments. If the publisher cannot justify the missing env declarations or cannot provide guidance for safe key handling, treat installation as higher risk and consider not enabling the skill.

Like a lobster shell, security has layers — review code before you run it.

latestvk97a7gwmpmy7y7vgs5cn28sfzs80t082
1kdownloads
0stars
1versions
Updated 1mo ago
v1.0.0
MIT-0

Orthogonal Platform

Orthogonal is a platform for monetizing and consuming APIs. Use these tools to discover, understand, and call any API on the platform.

Base URL: https://api.orth.sh/v1

Authentication

Get your API key at https://orthogonal.com/dashboard/settings

export ORTHOGONAL_API_KEY=orth_live_your_api_key

Tools

1. search

Search for APIs using natural language. Returns a lightweight list of matching endpoints.

Endpoint: POST /v1/search

curl -X POST 'https://api.orth.sh/v1/search' \
  -H 'Authorization: Bearer $ORTHOGONAL_API_KEY' \
  -H 'Content-Type: application/json' \
  -d '{"prompt": "scrape websites", "limit": 10}'

Parameters:

  • prompt (string, required): Natural language description of what you're looking for
  • limit (number, optional): Max results (default: 10, max: 50)

Response: List of matching APIs with endpoints (name, description, method, path, price)


2. get_details

Get full details about a specific endpoint including all parameters.

Endpoint: POST /v1/details

curl -X POST 'https://api.orth.sh/v1/details' \
  -H 'Authorization: Bearer $ORTHOGONAL_API_KEY' \
  -H 'Content-Type: application/json' \
  -d '{"api": "olostep", "path": "/v1/scrapes"}'

Parameters:

  • api (string, required): API slug from search results (e.g., "olostep", "linkup")
  • path (string, required): Endpoint path from search results (e.g., "/v1/scrapes")

Response: Full endpoint details including:

  • Path parameters
  • Query parameters (name, type, required, description)
  • Body parameters (name, type, required, description)
  • Pricing information
  • Documentation URL

3. integrate

Get ready-to-use code snippets for integrating an endpoint.

Endpoint: POST /v1/integrate

curl -X POST 'https://api.orth.sh/v1/integrate' \
  -H 'Authorization: Bearer $ORTHOGONAL_API_KEY' \
  -H 'Content-Type: application/json' \
  -d '{"api": "olostep", "path": "/v1/scrapes", "format": "orth-sdk"}'

Parameters:

  • api (string, required): API slug
  • path (string, required): Endpoint path
  • format (string, optional): Code format - one of:
    • orth-sdk (default) - Orthogonal SDK (@orth/sdk)
    • run-api - Direct HTTP to /v1/run
    • x402-fetch - x402 payment with JavaScript
    • x402-python - x402 payment with Python
    • curl - cURL command
    • all - All formats

Response: Code snippets ready to copy-paste


4. use (run)

Call an API endpoint using your Orthogonal credits.

Endpoint: POST /v1/run

curl -X POST 'https://api.orth.sh/v1/run' \
  -H 'Authorization: Bearer $ORTHOGONAL_API_KEY' \
  -H 'Content-Type: application/json' \
  -d '{
    "api": "olostep",
    "path": "/v1/scrapes",
    "body": {
      "url_to_scrape": "https://example.com"
    }
  }'

Parameters:

  • api (string, required): API slug
  • path (string, required): Endpoint path
  • query (object, optional): Query parameters
  • body (object, optional): Request body

Response:

{
  "success": true,
  "price": 0.01,
  "data": { /* API response */ }
}

5. list_all (optional)

List all discoverable APIs with their endpoints. Returns paginated APIs, each containing their endpoints. Use sparingly - prefer search for specific needs.

Endpoint: GET /v1/list-endpoints

curl 'https://api.orth.sh/v1/list-endpoints?limit=100' \
  -H 'Authorization: Bearer $ORTHOGONAL_API_KEY'

Parameters:

  • limit (number, optional): Max APIs to return per page (default: 100, max: 500)
  • offset (number, optional): Pagination offset for APIs

Response: List of APIs, each with nested endpoints array


Typical Workflow

  1. Search for what you need: POST /v1/search with natural language
  2. Get details for the endpoint: POST /v1/details to see required params
  3. Use the endpoint: POST /v1/run with the params

Or for integration:

  1. SearchGet detailsIntegrate to get code snippets

SDK Integration

For the simplest integration, use the Orthogonal SDK:

npm install @orth/sdk
import Orthogonal from "@orth/sdk";

const orthogonal = new Orthogonal({
  apiKey: process.env.ORTHOGONAL_API_KEY,
});

// Search for APIs
const search = await orthogonal.search("web scraping");

// Call an API
const result = await orthogonal.run({
  api: "olostep",
  path: "/v1/scrapes",
  body: { url_to_scrape: "https://example.com" }
});

x402 Direct Payment

Pay directly with USDC on Base blockchain - no API key required:

import { wrapFetchWithPayment } from "x402-fetch";
import { privateKeyToAccount } from "viem/accounts";

const account = privateKeyToAccount(process.env.PRIVATE_KEY);
const fetchWithPayment = wrapFetchWithPayment(fetch, account);

const response = await fetchWithPayment(
  "https://x402.orth.sh/olostep/v1/scrapes",
  {
    method: "POST",
    headers: { "Content-Type": "application/json" },
    body: JSON.stringify({ url_to_scrape: "https://example.com" })
  }
);

Support

Comments

Loading comments...