Capability catalog

tiny capabilities list

curl https://control.example.com/v1/capabilities \
  -H "Authorization: Bearer $TINY_TOKEN"

Operations

Provider	Operations
`stripe`	`payments.read`, `payments.get`, `customers.read`, `balance.read`
`openai`	`chat.complete`, `embeddings.create`, `models.read`
`slack`	`chat.post`, `conversations.read`, `users.read`
`github`	`issues.read`, `issues.create`, `pulls.read`, `workflows.read`
`google`	`sheets.read`, `sheets.append`, `sheets.describe`
`sendgrid`	`email.messages.send`
`http`	`request.send`

Every operation id has exactly three parts — provider.resource.action — because that is what the broker route /v1/capabilities/:provider/:resource/:action addresses. A concise allow entry is qualified with the capability name during normalization.

Enforced constraints

Constraints are the security boundary, and they are enforced at call time, not merely validated when the manifest is parsed.

Operation	Constraint	Enforcement
`slack.chat.post`	`channels`	refuses a channel the grant does not name
`slack.chat.post`	`allowBroadcast`	refuses `@channel` unless set
`github.issues.create`	`repositories`	refuses a repository outside the list
`openai.chat.complete`	`models`	refuses a model outside the list
`openai.chat.complete`	`maxOutputTokens`	caps `max_output_tokens` at the granted ceiling
`email.messages.send`	granted address	sends only from it
`email.messages.send`	`recipientDomains`	when set, sends only to those domains
(all)	`maxRequestsPerMinute`	per-grant rate limit

`http.request.send`

The escape hatch for an API with no dedicated integration — deliberately not generic.

Constraint	Meaning
`origins`	the only origins reachable. A grant with no `origins` reaches nothing at all.
`methods`	permitted HTTP methods
`pathPrefixes`	optional path restriction
`auth.scheme`	how the broker injects the credential, e.g. `header`
`auth.name`	the header name to inject into

capabilities:
  - name: inventory
    connection: warehouse-api
    allow:
      - http.request.send
    constraints:
      origins:
        - https://api.warehouse.example
      methods: [GET, POST]
      pathPrefixes: ['/v2/stock']
      auth:
        scheme: header
        name: x-api-key

The broker injects the credential into a header the app cannot set, read, or observe, and returns only the status and the payload — never set-cookie or upstream auth headers.

What the broker checks, in order

Grant

This app, this operation, this connection.

User-presence rule

Whether a real signed-in user must be behind the call.

Input schema

The shape of the input.

Constraints

The table above.

Rate limit

Per grant.

Response filter

Before your app sees the response.

Then it audits the call. Guide: Capabilities.

​Operations

​Enforced constraints

​http.request.send

​What the broker checks, in order

Operations

Enforced constraints

`http.request.send`

What the broker checks, in order