Skip to content
TrustedSkillsbeta
Back to all skills

Pay For Http Request

Official
stripe·vlatest·backend·MIT

This skill lets you programmatically make HTTP requests using Stripe's payment infrastructure, streamlining integrations and automation.

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add stripe/purl --skill pay-for-http-request -a claude-code
  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

stripe

Matched to the vendor's own GitHub organisation.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned stripe/purl at eb820395c2.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Scanned
1 file, 202 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill allows an AI agent to make HTTP requests and associate a payment with them. It enables agents to perform actions that require external services or data, while also handling the financial transactions involved. The core functionality is sending HTTP requests and processing payments in conjunction.

When to use it

  • Automated Data Acquisition: Retrieve real-time pricing information from an API and automatically pay for access.
  • Paid Content Scraping: Scrape content from a website that requires payment per article or data point.
  • API Integration with Usage Fees: Interact with APIs that charge based on usage, such as image generation services.
  • Automated Task Execution: Trigger external processes (e.g., sending SMS messages) and pay for the service directly through the agent.

Key capabilities

  • HTTP Request Sending
  • Payment Processing
  • Integration with Stripe API
  • Usage-based billing

Example prompts

  • "Retrieve the latest stock price from [API endpoint] and pay $0.10."
  • "Scrape article at [URL], paying $2 for access."
  • "Generate an image using [image generation API] and process a payment of $5."

Tips & gotchas

The skill requires proper configuration with Stripe credentials to function correctly. Ensure that the agent has sufficient permissions to make HTTP requests and handle payments through the configured Stripe account.