Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.sault.ai/llms.txt

Use this file to discover all available pages before exploring further.

A skill is a Markdown document, written for an agent, that describes how to use one or more paid services end-to-end. It says what user inputs to gather, which endpoints to call, in what order, how to handle results, and what artifact to return. SAULT hosts the catalog in Discover (discover.sault.ai). Anyone — builder, agent, browser — can open a skill by its public ID.

​
Skill ID

Every published skill has a stable, human-readable ID: 
<publisher>/<slug>
Example: sault.ai/launch-song-mailer. That ID is all an agent needs — it resolves to the skill body and to a one-paste “Use this skill” link, both available from the skill’s page in Discover.

​
Two ways an agent starts a skill

​
A. The user pastes a URL

The user copies a skill’s Use link from Discover and pastes it into their agent’s chat. The agent fetches it and gets a Markdown document: a short preamble (“the user wants you to run this skill”) followed by the full skill body. If SAULT is not configured in that environment, the preamble walks the agent through setup first. This is the lightest possible distribution: a link works in every agent that can fetch a URL.

​
B. The agent discovers a skill itself

The agent calls sault discover (CLI) or sault_discover (MCP) to browse the catalog, then runs the skill it picks:
1

Prepare

sault skill prepare <publisher>/<slug>
Returns a readiness JSON: is the agent paired, is the vault funded enough for the skill, is the signer authorised. If ready: false the response lists nextActions for the agent to follow.
2

Show

sault skill show <publisher>/<slug>
Prints the raw skill Markdown. The agent loads it into context and treats it as the instruction set for the next turn.
3

Run

The agent calls the services named in the skill via sault request. Each call pays its 402, gets a receipt, and lands in the agent’s history.
4

Deliver

The skill ends with an artifact specification — a file, a JSON summary, a link. The agent hands that back to the user with an itemised receipt.

​
What a skill is not

  • Not a runtime. SAULT does not execute the skill. The host agent (Claude, Cursor, Codex, …) does the orchestration; SAULT settles the paid calls inside it.
  • Not a payment instrument. The vault, the agent’s caps, and the signer authorisation decide whether a call gets paid. The skill cannot raise a limit.
  • Not an agent-grant. Every paired agent can fetch every published skill. Access is at the catalog level, not the agent level.