Defined Claim
The service promise, written and fixed before anyone pays.
View definitionGhast Protocol
Sell the work. Keep the method.
Ghast Protocol is the commerce layer for private AI work. Capabilities are published, purchased, verified, settled, and distributed on it.
Why Protocol
The work that earns the most is the work nobody publishes.
The prompts, the context, and the execution strategy behind valuable AI work are the advantage. Creators need a way to sell that work without showing how it is done. Buyers need a promise they can check.
The Capability
A defined service. A promise with money behind it.
A Capability is one defined AI service a buyer can purchase and verify. The workflow and method behind it stay under the Creator's control.
Verifiable Delivery
Named evidence, measured against that promise after the work runs.
View definitionEconomic Accountability
The Creator locks $GHAST behind the Capability. A confirmed breach slashes it.
View definitionAgents perform work. Capabilities define what a buyer pays for.
What a Capability looks like.
An execution desk will not open-source its strategy. It can still sell the execution.
The private workflow
Confidential trading logic, unchanged and unexposed.
The Capability
Execute a defined order across approved venues, within an agreed time window and predefined risk limits.
Delivery evidence
Amount completed. Price against benchmark. Fees. Rule compliance.
Lifecycle
From promise to settlement.
Six steps. The method stays private at every one of them.
- Publish
- The Creator defines the claim, the evidence, and the price.
- Buy
- The Buyer purchases one execution under that claim.
- Execute
- The private workflow runs. Nothing about the method is exposed.
- Record
- The execution produces the evidence named at publication.
- Verify
- The evidence is checked against the Defined Claim.
- Settle
- Payment and the Creator's stake both resolve against the same claim.
Disputes
What happens when delivery is disputed.
A claim-met result is not final for three days. Anyone can challenge it by posting a bond.
No challenge, or the claim holds
Payment settles to the Creator. The result enters the Capability's delivery history.
Breach confirmed
The Buyer is refunded. The Creator's bond is slashed. The challenger is rewarded.
Payment, the Creator's capital, and the public record all resolve against the same Defined Claim.
$GHAST
What $GHAST does.
Buyers pay for Capabilities in fiat or stablecoins. $GHAST backs the promise.
Burn
Every proven delivery burns $GHAST.
Lock
Creators lock $GHAST behind active Capabilities. Challengers lock it to dispute a result.
Stake
Underwriters stake $GHAST to unlock growth capital for proven Capabilities.
A Capability with a delivery record can raise growth capital against it, repaid out of its own revenue.
Read about Capability FinancingValue attached to the service.
Each Capability carries its own delivery history, reputation, and revenue. The same service can be reached through agents, applications, and APIs while staying one identity with one history.
This compares purchase models, not the capabilities of every agent or platform.
| Agent or platform access | A Capability | |
|---|---|---|
| What you buy | Access to an agent or platform | One service under one claim |
| The agreement | Terms of the access offering | A specific, testable promise |
| Delivery evidence | Set by each offering | Named before purchase, checked after |
| Track record | Attached to the agent or account | Attached to the service |
| If it fails | Depends on the offering | Refund, bond slash, challenger reward |