Skip to main content
For providers not covered by the built-in registry, you create credentials and capabilities manually.

Step 1: Store the secret

Because MY_CUSTOM_KEY doesn’t match any registry provider, this creates an unpinned secret with no auto-provisioning.

Step 2: Create a credential

See Credentials for all auth strategies and options.

Step 3: Create capabilities

Step 4: Invoke

Security considerations

Custom providers are less secure than registry-compiled providers because:
  • The secret is not pinned to a provider (it could be referenced by multiple credentials)
  • The capability definitions can be modified at runtime
  • There’s no compiled-in host allow-list
For production use, consider contributing your provider to the official registry. This gives you:
  • Immutable secret pinning
  • Compiled-in auth strategy and host definitions
  • Tamper-proof capability definitions

Contributing to the registry

To add a provider to the built-in registry, create a JSON file in registry/ following the registry schema. Example:
Next: Registry schema