Payments Introduction
Traditional payment models block AI from getting things done with autonomy. Skyfire Agent Payments changes that.
Agent Payments enables AI to access APIs without the need for accounts, SaaS subscriptions or manual checkouts. This allows your AI the freedom to get valuable stuff done.
Benefits
- Enable your agent to access premium services autonomously
- Control agent spend
- Simple integration to existing applications and frameworks
Skyfire providers a managed wallet that can be easily funded, configured with Payment Rules, and monitored through the Skyfire dashboard. API keys linked to your wallet enable programmatic access and payments to services.
You can quickly give your Agent Payment capabilities by giving them a Skyfire API key.
How Agent Payments Work:
There are 2 implementations of Agent Payments depending on the use case.
Payment as Auth: Payments that are included with the API service call.
Payment as Auth is used with Service Providers that have a straightforward API that can be made available to all Skyfire enabled agents on demand.
Agents can access the service's URL using the existing API spec while including theirskyfire-api-key
in the header.
See Venice AI API Reference as an example of how to access paid services on demand
Standalone Payments: Payments that are not included with the API service call.
Standalone Payments is used with a variety of service providers that have stricter requirements on access or services that require one time payments outside of individual API calls.
Agents can make a payment using the skyfire endpointv1/payment
and their skyfire-api-key
. The agent then provides the service provider with a token that can be validated as proof of payment.
See Standalone Payments API Reference as an example of how to make standalone payments
Updated about 1 month ago