Data Providers

Agents rarely live on the LLM alone — they read issues, send emails, move money. TapPass ships a catalogue of data providers with a uniform governance layer: every operation is policy-checked, audited, and subject to PII redaction before hitting the vendor.

Shipped providers

Provider	Operations	EU residency	Go to
GitHub	Repos, issues, PRs, code search	US (SCC)	GitHub
Slack	Messages, channels, search	US (SCC)	Slack
Jira	Issues, transitions, comments	US (SCC)	Jira
Gmail	Send, search, labels	US (SCC)	Gmail
Google Drive	List, download, create	US (SCC)	Google Drive
Stripe	Payments, subscriptions, Connect, Issuing	EU / US	Stripe
Revolut	Payment intents, transfers, cards	EU (Lithuania)	Configured via YAML
WhatsApp Business	Send, read, mark read	US (SCC)	Configured via YAML
Holded (accounting)	Invoicing, contacts, documents	EU	Configured via YAML

How they work

Every data provider is declared in a YAML spec (shipped providers live in the server repo under tappass/adapters/inbound/gateway/providers/) and backed by GenericHTTPAdapter (or a specialised adapter like GmailAdapter).

name: github
api_base_url: https://api.github.com
auth:
  type: bearer
  header: Authorization
operations:
  - name: list_issues
    op_group: read
    method: GET
    endpoint: /repos/{owner}/{repo}/issues
  - name: create_issue
    op_group: write
    method: POST
    endpoint: /repos/{owner}/{repo}/issues

Your agent calls them through TapPass — never directly. When the model requests a provider operation as a tool call through the governed gateway, TapPass resolves the provider, fetches the connected credential from the vault, executes the operation, and audits the call.

Governance applied

On every call:

• Authz — an authorization policy decides if this agent can use this provider and op
• Detection — payloads are scanned for PII / secrets before leaving
• Policy — a tool-decision policy can approve/block by op + args (e.g., no send_message to @external-* channels)
• Audit — operation, args, result, and policy verdict are all recorded
• Rate limit / budget — per-agent and per-provider quotas

Add your own

Register a YAML/JSON provider spec at runtime via POST /api/providers (super_admin) pointing at any REST API. The GenericHTTPAdapter handles OAuth / Bearer / API-key auth, templated endpoints, and response parsing — no Python required for the common case.

name: myvendor
display_name: "My Vendor"
api_base_url: https://api.myvendor.com
auth:
  type: bearer
  header: Authorization
operations:
  - name: list_things
    op_group: read
    method: GET
    endpoint: /things

For complex protocols (MIME construction, signed requests, non-REST), write a specialised adapter — see the Gmail adapter in the server repo (tappass/platform/vault/providers/gmail.py) for a reference.