[
  {
    "id": "github",
    "name": "GitHub",
    "about": "repos, Actions, issues and pull requests",
    "console": "https://github.com/settings/personal-access-tokens/new?name=godmode&expires_in=366&administration=write&contents=write&workflows=write&actions=write&secrets=write&actions_variables=write&environments=write&issues=write&pull_requests=write",
    "key": [
      {
        "name": "GH_TOKEN",
        "label": "Access token",
        "goal": "Create a GitHub token",
        "steps": [
          "Choose the **Resource owner** and **All repositories**.",
          "Select **Generate token** and copy it."
        ],
        "kind": "static-token",
        "visit": "Visit GitHub's token page"
      }
    ],
    "access": "A fine-grained personal access token acts as its owner within one selected user or organization. The setup requests broad repository write access, including administration, across all repositories for that owner. Organization approval, token lifetime policy and your own role still apply; other accounts or API operations can require different permissions or a GitHub App.",
    "verify": [
      "Use the official GitHub CLI or API to identify the token owner and read an intended repository. Check the endpoint's required permissions before creating repositories, configuring Actions, managing secrets or opening pull requests. A successful identity check alone does not prove repository write access."
    ],
    "recover": [
      "For permission failures, check the resource owner, repository selection and organization approval first. For an expired or revoked token, create a replacement through GitHub and save it with godmode set GH_TOKEN. Verify the intended operation before retiring a still-valid old token."
    ],
    "docs": [
      {
        "title": "Personal access tokens and permissions",
        "url": "https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/managing-your-personal-access-tokens"
      },
      {
        "title": "GitHub CLI authentication environment",
        "url": "https://cli.github.com/manual/gh_help_environment"
      }
    ]
  },
  {
    "id": "cloudflare",
    "name": "Cloudflare",
    "about": "Workers, D1, R2, DNS and email",
    "console": "https://dash.cloudflare.com/profile/api-tokens",
    "key": [
      {
        "name": "CLOUDFLARE_API_TOKEN",
        "label": "API token",
        "goal": "Create a Cloudflare API token",
        "steps": [
          "Create a token from **Read All Resources**.",
          "Change **Read** to **Edit** where available.",
          "Review the summary, create the token and copy it."
        ],
        "kind": "static-token",
        "visit": "Visit Cloudflare's token page"
      }
    ],
    "access": "A user API token reaches the account and zone resources included in its policies. The setup deliberately starts broad and changes available Read permissions to Edit; inspect the summary for Workers, D1, R2, DNS and any other intended service. Resource selection, your account role and service availability still limit access. For domain registration, verify Registrar write permission for the intended account; changing Read to Edit does not establish Registrar access. The Registrar API beta registers supported available domains and requires a valid default payment method, a default registrant contact and acceptance of the Domain Registration Agreement. The user must set up billing in the dashboard. Check the domain's current availability and price and the user's purchase authorization before registering. R2 S3 credentials are a separate credential type.",
    "verify": [
      "Check the user token with GET /client/v4/user/tokens/verify, then list the intended account or zone resources using Cloudflare's API or Wrangler. An active token does not prove every service permission. Select the exact account and zone before provisioning or deploying."
    ],
    "recover": [
      "Fix missing permissions or resource policies without replacing a valid secret. For a lost, expired or revoked secret, use the dashboard to create a replacement or roll the token, then godmode set CLOUDFLARE_API_TOKEN. Rolling invalidates the old value; creating a separate token allows a staged replacement."
    ],
    "docs": [
      {
        "title": "Create API tokens",
        "url": "https://developers.cloudflare.com/fundamentals/api/get-started/create-token/"
      },
      {
        "title": "Roll tokens",
        "url": "https://developers.cloudflare.com/fundamentals/api/how-to/roll-token/"
      },
      {
        "title": "Wrangler commands",
        "url": "https://developers.cloudflare.com/workers/wrangler/commands/"
      },
      {
        "title": "Registrar API beta prerequisites and workflow",
        "url": "https://developers.cloudflare.com/registrar/registrar-api/"
      },
      {
        "title": "Registrar API support and billing requirements",
        "url": "https://developers.cloudflare.com/api/resources/registrar/"
      }
    ]
  },
  {
    "id": "vercel",
    "name": "Vercel",
    "about": "projects, deploys and domains",
    "console": "https://vercel.com/account/settings/tokens",
    "key": [
      {
        "name": "VERCEL_TOKEN",
        "label": "Access token",
        "goal": "Create a Vercel token",
        "steps": [
          "Make a token with **Full Account** scope. Choose an expiration date."
        ],
        "kind": "static-token",
        "visit": "Visit Vercel's token page"
      }
    ],
    "access": "A Full Account token reaches your personal account and teams, subject to your role. Team and project scopes are alternatives when desired. Full-account requests need the intended team ID or slug when targeting team resources; a valid token can otherwise select a different default team.",
    "verify": [
      "Use Vercel's CLI or REST API to list projects or deployments in the intended team. Confirm the project before configuring its environment, deploying or changing domains. The CLI accepts VERCEL_TOKEN; direct API clients must read that variable and send Bearer authentication."
    ],
    "recover": [
      "Read the error: missingToken means the credential was not supplied; invalidToken can mean wrong, expired or deleted. Fix team/project targeting for scope failures. Replace an invalid token from Account Tokens and save it with godmode set VERCEL_TOKEN."
    ],
    "docs": [
      {
        "title": "Access token scope, use and recovery",
        "url": "https://vercel.com/docs/accounts/access-tokens"
      },
      {
        "title": "CLI token option",
        "url": "https://vercel.com/docs/cli/global-options#token"
      }
    ]
  },
  {
    "id": "supabase",
    "name": "Supabase",
    "about": "projects, databases and auth",
    "console": "https://supabase.com/dashboard/account/tokens",
    "key": [
      {
        "name": "SUPABASE_ACCESS_TOKEN",
        "label": "Access token",
        "goal": "Create a Supabase access token",
        "steps": [
          "Select **Generate new token** > **Create legacy token**.",
          "Type a name and set **Expires in** to **Never**.",
          "Select **Generate token**, then copy the token."
        ],
        "kind": "static-token",
        "visit": "Visit Supabase's access tokens"
      }
    ],
    "access": "The legacy full-access personal token reaches all organizations and projects your account can access, including future ones. Scoped tokens are also available. This credential authenticates the Management API, CLI and compatible tools; it is not a database password, project publishable key or runtime secret key.",
    "verify": [
      "List accessible organizations and projects through the Management API or official CLI, then confirm the intended project and account role. Use the relevant management permissions for project configuration, database work and deployments. Check the installed CLI help: hosted and local targeting can differ by version."
    ],
    "recover": [
      "Check account role and token scope on permission errors. Replace an expired or revoked token in account settings and save it with godmode set SUPABASE_ACCESS_TOKEN. The CLI reads this environment variable before a saved login token; Godmode does not update the CLI cache."
    ],
    "docs": [
      {
        "title": "Personal access tokens",
        "url": "https://supabase.com/docs/guides/platform/personal-access-tokens"
      },
      {
        "title": "Management API",
        "url": "https://supabase.com/docs/reference/api/introduction"
      },
      {
        "title": "CLI reference",
        "url": "https://supabase.com/docs/reference/cli/introduction"
      }
    ]
  },
  {
    "id": "stripe",
    "name": "Stripe",
    "about": "payments, in test and live mode",
    "console": "https://dashboard.stripe.com/test/apikeys",
    "key": [
      {
        "name": "STRIPE_TEST_SECRET_KEY",
        "label": "Test secret key",
        "goal": "Copy your Stripe test secret key",
        "note": "If there is no sk_test_ key, switch to a sandbox in the account picker.",
        "steps": [
          "Under **Standard keys**, reveal the **Secret key** (sk_test_…) and copy it."
        ],
        "kind": "static-key",
        "visit": "Visit Stripe’s test keys"
      },
      {
        "name": "STRIPE_TEST_PUBLISHABLE_KEY",
        "label": "Test publishable key",
        "goal": "Copy your Stripe test publishable key",
        "steps": [
          "Under **Standard keys**, copy the **Publishable key** (pk_test_…)."
        ],
        "kind": "public-key",
        "visit": "Visit Stripe’s test keys"
      },
      {
        "name": "STRIPE_LIVE_SECRET_KEY",
        "label": "Live secret key",
        "goal": "Create a Stripe live secret key",
        "console": "https://dashboard.stripe.com/apikeys",
        "steps": [
          "Select **Create secret key** and type the verification code.",
          "Type a **Key name**, then select **Create**.",
          "Select the key (sk_live_…) to copy it."
        ],
        "kind": "static-key",
        "visit": "Visit Stripe’s live keys"
      },
      {
        "name": "STRIPE_LIVE_PUBLISHABLE_KEY",
        "label": "Live publishable key",
        "goal": "Copy your Stripe live publishable key",
        "console": "https://dashboard.stripe.com/apikeys",
        "note": "If it starts with pk_test_, switch to live mode first.",
        "steps": [
          "Under **Standard keys**, copy the **Publishable key** (pk_live_…)."
        ],
        "kind": "public-key",
        "visit": "Visit Stripe’s live keys"
      }
    ],
    "ready": [
      [
        "STRIPE_TEST_SECRET_KEY"
      ],
      [
        "STRIPE_LIVE_SECRET_KEY"
      ]
    ],
    "access": "Standard secret keys have broad API access in one account or sandbox. Test and live credentials are separate; publishable keys are for client applications and cannot perform secret-key operations. Restricted keys are an alternative. Webhook signing secrets are separate values.",
    "verify": [
      "Use the Stripe SDK or API to read the intended account and inspect a resource in the selected sandbox or live mode. Supply the selected secret key explicitly: these Godmode key names are not an automatic Stripe SDK configuration. Build and test payment flows in a sandbox before an authorized live operation."
    ],
    "recover": [
      "For an invalid or expired key, use the account's API keys page to create or rotate it and overwrite the matching Godmode entry. Stripe offers an expiration grace period for the old key. Check mode, restrictions and account status before assuming every denied operation needs rotation."
    ],
    "docs": [
      {
        "title": "API key types, environments and rotation",
        "url": "https://docs.stripe.com/keys"
      },
      {
        "title": "Stripe API",
        "url": "https://docs.stripe.com/api"
      }
    ]
  },
  {
    "id": "posthog",
    "name": "PostHog",
    "about": "analytics, flags and insights",
    "console": "https://app.posthog.com/settings/user-api-keys?preset=mcp_server",
    "key": [
      {
        "name": "POSTHOG_PERSONAL_API_KEY",
        "label": "Personal API key",
        "goal": "Create a PostHog API key",
        "steps": [
          "Select **Create key**; the form is already filled in.",
          "Copy the key (phx_…) from the dialog."
        ],
        "kind": "static-token",
        "visit": "Visit PostHog's personal API keys"
      }
    ],
    "access": "A personal API key accesses private analytics, insights, flags and other APIs using your account permissions and the key's scopes. The MCP preset is convenient for broad agent use; confirm its organization/project selection. Use the matching US, EU or self-hosted instance. A project ingestion key is a different credential.",
    "verify": [
      "Use PostHog's API to read the intended project and run a small query or list the intended resource. Check the endpoint's required scope before managing flags, dashboards or experiments. Keep the personal key server-side; it is not a browser analytics key."
    ],
    "recover": [
      "Check the instance, project and scopes first. Create a replacement for an invalid key and save it with godmode set POSTHOG_PERSONAL_API_KEY. If rolling a legacy key, the old value is invalidated; update every consumer that used it."
    ],
    "docs": [
      {
        "title": "Personal API keys",
        "url": "https://posthog.com/docs/api/personal-api-keys"
      },
      {
        "title": "API scopes",
        "url": "https://posthog.com/docs/api/scopes"
      },
      {
        "title": "API overview",
        "url": "https://posthog.com/docs/api"
      }
    ]
  },
  {
    "id": "notion",
    "name": "Notion",
    "about": "pages, databases and comments",
    "console": "https://app.notion.com/developers/tokens",
    "key": [
      {
        "name": "NOTION_API_KEY",
        "label": "Access token",
        "goal": "Create a Notion access token",
        "prompt": "Paste your token",
        "steps": [
          "Select **New token** and name it.",
          "Choose the workspace, **Notion API**, and an expiration.",
          "Select **Create token**, then copy the token."
        ],
        "kind": "static-token",
        "visit": "Visit Notion's token page"
      }
    ],
    "access": "The personal access token acts as its creator in one workspace, with the selected Notion API capability and that user's content permissions. The workspace can restrict who creates or uses PATs. An internal connection token is an alternative identity with capabilities and explicitly shared pages, independent of one user's membership.",
    "verify": [
      "Use the Notion SDK or API to retrieve the token identity and an intended page or data source. Confirm the workspace and content access before creating or updating pages, databases or comments. The SDK must read NOTION_API_KEY explicitly."
    ],
    "recover": [
      "PATs expire within one year. Create a replacement through the Developer portal and save it with godmode set NOTION_API_KEY. An unauthorized response can also come from workspace PAT policy; missing content can reflect lost user access or a page not shared with an internal connection. Repair that access instead of repeatedly replacing tokens."
    ],
    "docs": [
      {
        "title": "Personal access tokens",
        "url": "https://developers.notion.com/guides/connections-and-tokens/personal-access-tokens"
      },
      {
        "title": "Internal connections",
        "url": "https://developers.notion.com/guides/connections-and-tokens/internal-connections"
      }
    ]
  },
  {
    "id": "gmail",
    "name": "Gmail",
    "about": "an inbox agents read and send from",
    "console": "https://myaccount.google.com/apppasswords",
    "key": [
      {
        "name": "GMAIL_USER",
        "label": "Mailbox address",
        "goal": "Type the Gmail address agents will use",
        "console": null,
        "prompt": "Type the address",
        "secret": false,
        "steps": [],
        "kind": "address"
      },
      {
        "name": "GMAIL_APP_PASSWORD",
        "label": "App password",
        "goal": "Create a Gmail app password",
        "drop": "  ",
        "note": "This page works only with 2-Step Verification turned on.",
        "steps": [
          "Type a name under **App name**, then select **Create**.",
          "Copy the 16-character password."
        ],
        "kind": "app-password",
        "visit": "Visit Google's app passwords"
      }
    ],
    "access": "The mailbox address and app password support IMAP/SMTP clients where Google Account policy allows them. App passwords require 2-Step Verification and can be unavailable for some organization accounts, security-key-only setups or Advanced Protection. They do not grant Gmail API, Google SSO or Workspace administration access.",
    "verify": [
      "Configure the mail client with GMAIL_USER and GMAIL_APP_PASSWORD and establish an authenticated TLS IMAP or SMTP session without sending a message. Confirm the mailbox before reading mail or carrying out an authorized send. Use the Gmail API's separate OAuth flow if the task requires that API."
    ],
    "recover": [
      "Google revokes app passwords after an account password change. Create a replacement and save it with godmode set GMAIL_APP_PASSWORD. If app passwords are unavailable, use a supported Google sign-in/OAuth client; repeating app-password setup cannot override account policy."
    ],
    "docs": [
      {
        "title": "App passwords and recovery",
        "url": "https://support.google.com/accounts/answer/185833"
      },
      {
        "title": "Gmail IMAP and SMTP",
        "url": "https://developers.google.com/workspace/gmail/imap/imap-smtp"
      }
    ]
  },
  {
    "id": "google",
    "name": "Google",
    "about": "Ads keyword research and Search Console",
    "console": "https://console.cloud.google.com/projectselector/iam-admin/serviceaccounts",
    "key": [
      {
        "name": "GOOGLE_ADS_SERVICE_ACCOUNT_JSON",
        "label": "Ads service account",
        "goal": "Save a Google Ads service account key",
        "prompt": "Drag or paste the key file",
        "file": true,
        "format": "google-service-account",
        "note": "Then add its email in Google Ads under Admin > Access and security.",
        "steps": [
          "Pick your Ads project, then open or create a service account.",
          "Select **Keys** > **Add key** > **Create new key** > **JSON** > **Create**."
        ],
        "kind": "service-account-json",
        "visit": "Visit Google's service accounts"
      },
      {
        "name": "GOOGLE_SEARCH_CONSOLE_SERVICE_ACCOUNT_JSON",
        "label": "Search Console account",
        "goal": "Save a Search Console service account key",
        "prompt": "Drag or paste the key file",
        "file": true,
        "format": "google-service-account",
        "note": "Then add its email to the property under Settings > Users and permissions.",
        "steps": [
          "Pick your Search Console project, then open or create a service account.",
          "Select **Keys** > **Add key** > **Create new key** > **JSON** > **Create**."
        ],
        "kind": "service-account-json",
        "visit": "Visit Google's service accounts"
      }
    ],
    "ready": [
      [
        "GOOGLE_ADS_SERVICE_ACCOUNT_JSON"
      ],
      [
        "GOOGLE_SEARCH_CONSOLE_SERVICE_ACCOUNT_JSON"
      ]
    ],
    "access": "The bundled JSON entries are service-account private keys, not OAuth clients or user grants. For Ads, enable the API and obtain the required API access level in that Cloud project, then add the service-account email to the intended Ads account or manager. For Search Console, enable its API and grant the identity access to each property. Cloud IAM roles alone do not grant Ads or Search Console access.",
    "verify": [
      "The consumer must parse the JSON variable and use an official Google auth/client library with the API's scopes; these variable names are Godmode conventions, not automatic Google SDK settings. Ads uses the adwords scope; Search Console uses webmasters or webmasters.readonly.",
      "List directly accessible Ads customers, then check the intended client/manager path. For Search Console, list sites and confirm the exact property and permission level. Only then run reporting, keyword planning or authorized management operations."
    ],
    "recover": [
      "Let the consuming Google library obtain and renew access tokens from the service-account key; ordinary access-token expiry needs no new key or browser consent. For a disabled, deleted or invalid private key, create a replacement on the same service account, save the matching Godmode entry, verify it, then retire the old key.",
      "User OAuth is a separate supported consumer choice: store its refresh grant under a separate name such as GOOGLE_SEARCH_CONSOLE_OAUTH_JSON. Reauthorize only when refresh fails because the grant is revoked, expired or policy requires sign-in. Save any replacement grant with godmode set NAME; Godmode does not write back refreshed credentials."
    ],
    "docs": [
      {
        "title": "Ads service accounts and account access",
        "url": "https://developers.google.com/google-ads/api/docs/oauth/service-accounts"
      },
      {
        "title": "List accessible Ads accounts",
        "url": "https://developers.google.com/google-ads/api/docs/account-management/listing-accounts"
      },
      {
        "title": "Search Console authorization",
        "url": "https://developers.google.com/webmaster-tools/v1/how-tos/authorizing"
      },
      {
        "title": "List Search Console sites",
        "url": "https://developers.google.com/webmaster-tools/v1/sites/list"
      },
      {
        "title": "OAuth refresh and grant expiry",
        "url": "https://developers.google.com/identity/protocols/oauth2"
      },
      {
        "title": "Service account key rotation",
        "url": "https://docs.cloud.google.com/iam/docs/key-rotation"
      }
    ]
  },
  {
    "id": "higgsfield",
    "name": "Higgsfield",
    "about": "image and video generation",
    "console": "https://open.higgsfield.ai/api-keys",
    "key": [
      {
        "name": "HIGGSFIELD_API_KEY_ID",
        "label": "API key ID",
        "goal": "Create a Higgsfield API key",
        "split": [
          ":",
          0
        ],
        "note": "The copied key is ID:secret. This saves the ID; the next step, the secret.",
        "steps": [
          "Create and name an **API key**.",
          "Copy the key. Keep the dialog open."
        ],
        "kind": "static-key",
        "visit": "Visit Higgsfield's API keys"
      },
      {
        "name": "HIGGSFIELD_API_KEY_SECRET",
        "label": "API key secret",
        "goal": "Paste the same Higgsfield API key again",
        "console": null,
        "split": [
          ":",
          1
        ],
        "note": "If the key is lost, create one and replace both the ID and secret.",
        "steps": [],
        "kind": "static-key",
        "prompt": "Paste the same key again"
      }
    ],
    "access": "The key ID and secret are one credential pair for a personal or organization account. Both are needed for server-side authentication. The selected account owns generated work and charges; individual models and environments can have separate access requirements.",
    "verify": [
      "Use the selected model's official API documentation and the Higgsfield client or API. Supply both stored values explicitly; official examples may use HF_API_KEY_ID and HF_API_KEY_SECRET instead of these Godmode names. Read an existing request's status when available. Creating a generation can incur charges and is not a free authentication probe."
    ],
    "recover": [
      "For invalid, expired or disabled credentials, use API keys in Higgsfield Console and replace both Godmode entries from the same new pair. Verify before deleting a still-valid old pair. A model availability error is not proof that the credential is invalid."
    ],
    "docs": [
      {
        "title": "Authentication",
        "url": "https://docs.higgsfield.ai/docs/authentication"
      },
      {
        "title": "Key lifecycle and account controls",
        "url": "https://docs.higgsfield.ai/docs/enterprise/access-control"
      },
      {
        "title": "Model documentation index",
        "url": "https://docs.higgsfield.ai/docs/llms.txt"
      }
    ]
  },
  {
    "id": "zernio",
    "name": "Zernio",
    "about": "social publishing",
    "console": "https://zernio.com/dashboard/api-keys",
    "key": [
      {
        "name": "ZERNIO_API_KEY",
        "label": "API key",
        "goal": "Create a Zernio API key",
        "steps": [
          "Open **API Keys**, then select **Create API key**.",
          "Name the key, select **Create key**, then copy it."
        ],
        "kind": "static-key",
        "visit": "Visit Zernio's API keys"
      }
    ],
    "access": "The API key accesses Zernio profiles and resources within its permissions. This setup uses broad read/write access; narrower profile, resource and read-only scopes exist. Social accounts must also be connected with their own platform permissions.",
    "verify": [
      "Use Zernio's SDK or API to list profiles and connected accounts, then confirm the intended account ID and connection health. Check platform support before scheduling posts, reading analytics or managing an inbox. SDKs read ZERNIO_API_KEY."
    ],
    "recover": [
      "Replace an expired or revoked Zernio API key through its API keys settings and save it with godmode set ZERNIO_API_KEY. If only a connected social account needs authorization again, use Zernio's official reconnect flow for that account; replacing the Zernio key will not repair the platform grant."
    ],
    "docs": [
      {
        "title": "API setup and connected accounts",
        "url": "https://docs.zernio.com/quickstart"
      },
      {
        "title": "API keys and authentication errors",
        "url": "https://docs.zernio.com/api-keys/list-api-keys"
      },
      {
        "title": "Connection troubleshooting",
        "url": "https://docs.zernio.com/for-you/troubleshooting"
      }
    ]
  },
  {
    "id": "prodigi",
    "name": "Prodigi",
    "about": "print-on-demand orders",
    "console": "https://dashboard.prodigi.com/settings/api",
    "key": [
      {
        "name": "PRODIGI_SANDBOX_API_KEY",
        "label": "Sandbox API key",
        "goal": "Copy your Prodigi sandbox API key",
        "console": "https://sandbox-beta-dashboard.pwinty.com/settings/api",
        "note": "pwinty.com is Prodigi's sandbox; sign in with your Prodigi account.",
        "steps": [
          "Under **API authentication**, select **Show key** and copy it."
        ],
        "kind": "static-key",
        "visit": "Visit Prodigi's API settings"
      },
      {
        "name": "PRODIGI_API_KEY",
        "label": "Live API key",
        "goal": "Copy your Prodigi live API key",
        "note": "Orders placed with this key are printed, shipped and billed.",
        "steps": [
          "Under **API authentication**, select **Show key** and copy it."
        ],
        "kind": "static-key",
        "visit": "Visit Prodigi's API settings"
      }
    ],
    "ready": [
      [
        "PRODIGI_SANDBOX_API_KEY"
      ],
      [
        "PRODIGI_API_KEY"
      ]
    ],
    "access": "Sandbox and live API keys belong to separate environments. Sandbox orders are not fulfilled or charged. Live orders are printed, shipped and billed. Select the endpoint that matches the key.",
    "verify": [
      "Use the Print API's documented authentication header with the matching environment. Read existing orders or product details to check the intended access, or request a quote for the intended specification. Use sandbox orders for fulfillment integration tests; a sandbox result does not prove a live print was produced."
    ],
    "recover": [
      "Check that the key matches the sandbox or live API first. Retrieve or replace the environment's key through the Prodigi dashboard and official support if required, then save the matching Godmode entry. Confirm the provider's replacement behavior before retiring a key used by other consumers."
    ],
    "docs": [
      {
        "title": "Print API documentation",
        "url": "https://www.prodigi.com/print-api/docs/"
      },
      {
        "title": "v4 environments, authentication and operations",
        "url": "https://www.prodigi.com/print-api/docs/v4/"
      }
    ]
  }
]
