Skip to main content
GET
/
api
/
credits
/
config
Get Credits
curl --request GET \
  --url https://app.puffle.ai/api/credits/config \
  --header 'Authorization: Bearer <token>'
{
  "registryVersion": "billing-registry:v1",
  "operations": {
    "work_email_lookup": {
      "id": "work_email_lookup",
      "label": "Work email lookup",
      "credits": 2,
      "billableUnit": "provider_submission",
      "unitLabel": "provider submission",
      "featureGroup": "enrichments",
      "certainty": "maximum"
    }
  },
  "plans": {
    "pro": {
      "id": "pro",
      "billingProductId": "pro",
      "display": {
        "name": "Pro",
        "order": 2,
        "badge": "Most popular",
        "positioning": "For sales teams running intent-based GTM"
      }
    }
  },
  "entitlements": {
    "keys": [
      "signals.manual_rescan"
    ]
  },
  "legacyCreditActions": {
    "EMAIL_LOOKUP": "work_email_lookup"
  },
  "costs": {
    "EMAIL_LOOKUP": 2
  }
}
CLI: 
puffle credit config

​
Overview

Returns the public credit price table for billable Puffle actions. The response is a static map from action identifier to credits consumed per unit of work. Use this before creating lead searches, enrichment runs, deep research, generated messages, or other billable operations when you need to estimate spend.

​
AI agent notes

Fetch this live instead of hard-coding prices. Multiply the returned action cost by the planned batch size or unit count to produce an estimate. If an action is absent from the map, do not assume it is free; check the endpoint page or ask the human before launching a potentially billable workflow.

Authorizations

​
Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Response

Credit costs and Billing Registry metadata.

​
registryVersion
string
required
​
operations
object
required
​
plans
object
required
​
entitlements
object
required
​
legacyCreditActions
object
required
​
costs
object
required