Verida AI Docs
  • Welcome
  • Getting Started
    • How it works
    • Developer Console
    • Get an API key
    • Authentication
    • Scopes
    • API Requests
    • Connectors
      • Build a Connector
    • Example Apps
  • Integrations
    • PersonalAgentKit
    • LangGraph
    • NEAR Protocol
    • Nillion Network
  • Data APIs
    • Overview
    • Data Types
    • API Endpoints
      • Queries
      • Search
      • AI Prompts
      • Actions
      • Other Endpoints
    • API Performance
    • Data examples
    • API Reference
  • Resources
    • Tutorials
      • Accessing User Data (Telegram)
    • Learn
      • Anatomy of an AI Agent
      • Dynamic Loading of Data for Realtime AI
      • Data Privacy Issues
      • Web3 & DePIN solves AI's privacy problems
      • Privacy Preserving AI Tech Stack
      • Confidential Compute Litepaper
    • AI Use Cases
    • Verida Vault
    • Privacy & Security
    • Pricing
    • Grants
    • Support
Powered by GitBook
On this page
  • Credits and API Requests
  • Payment Options for API Requests
  • Purchasing Additional Credits
Export as PDF
  1. Resources

Pricing

PreviousPrivacy & SecurityNextGrants

Last updated 4 months ago

Verida AI offers a flexible pricing model that allows you to manage API costs effectively while scaling your application. Below is an overview of how pricing works on our platform.

Credits and API Requests

  • Credit Value: Each credit is valued at 0.01 USD.

  • API Request Consumption:

    • Standard API Requests: Most API requests consume 1 credit per call.

    • Intensive API Requests: More resource-intensive operations (e.g., LLM processing or heavy searches) may consume multiple credits.

The exact number of credits consumed for each API endpoint is detailed in the respective API Documentation.

Payment Options for API Requests

When your application requests access to user data, you have two payment options for covering API request costs:

  1. User-Paid Requests:

    • The user authorizes and pays for the API requests initiated by your application.

  2. Developer-Paid Requests:

    • Your application bears the cost for the API requests.

This flexibility ensures that you can choose the model that best suits your application's business logic and user experience.

See for more information on the payerattribute when authenticating with a user.

Purchasing Additional Credits

  • Conversion Process:

    1. Convert VDA to Credits: Use the Developer Console to convert your VDA into credits.

  • Dynamic Pricing with VDA: The conversion rate between VDA and credits is calculated dynamically at the time of each API request. This means that the amount of VDA deducted per API call reflects the current VDA price.

    Examples:

    • If VDA is 0.01 USD and your API call consumes 1 credit, you will use 1 VDA.

    • If VDA is 0.10 USD and your API call consumes 1 credit, you will use 0.1 VDA.

This dynamic pricing model ensures that the cost of API usage remains transparent and reflective of current market conditions.

If you need to increase your credit balance, you can purchase additional credits by acquiring Verida tokens (VDA) and converting them into credits directly through the .

Purchase VDA: Acquire Verida tokens from .

Developer Console
supported exchanges
#generate-an-authentication-request-url