ScopedGrantClaims (draft)

Documentation Index

Fetch the complete documentation index at: https://glide-9da73dea.mintlify.app/llms.txt

Use this file to discover all available pages before exploring further.

​

Canonical URL

​

Required fields

​

Optional fields

​

Validation contract

1. JWT signature — verified against the AS’s JWKS (production) or HMAC-SHA256 secret (development; set MCP_TOKEN_VERIFIER_DEV_SECRET).
2. exp not in the past — bearer expiry check.
3. exp - iat <= 3600 — max TTL enforcement. Grants issued for longer than 60 min are rejected even if the signature is valid.
4. aud.vault_id + aud.entity_id present and match the resource on the request — RFC 8707 enforcement. Both fields must match; one-sided match is denied.
5. act.sub corresponds to a registered agent — DB lookup; stale or revoked agent principals are denied.
6. F3 IRON RULE — fresh-read tenant verification. Re-reads the principal’s tenant from DB. The cached token alone never authorizes.
7. policy_version matches the current envelope — mismatch raises PolicyStaleError (F5).

​

Example

import { grantClaimsSchema } from '@glideco/schemas';

const claims = grantClaimsSchema.parse({
  iss: 'https://glide.co',
  sub: '11111111-1111-4111-8111-111111111111',
  act: { sub: '22222222-2222-4222-8222-222222222222' },
  azp: 'claude-desktop-prod',
  aud: {
    vault_id: '33333333-3333-4333-8333-333333333333',
    entity_id: '44444444-4444-4444-8444-444444444444',
  },
  scope: ['accounts:read', 'payments:initiate'],
  policy_version: 7,
  iat: 1746355200,
  nbf: 1746355200,
  exp: 1746358800,  // iat + 3600 — exactly at the 60-min cap
  jti: '55555555-5555-4555-8555-555555555555',
});

import { grantClaimsValidatedSchema } from '@glideco/schemas';

// This will throw ZodError if exp - iat > 3600.
const validated = grantClaimsValidatedSchema.parse(rawClaims);

​

Validating against the schema

1. At grant-issue time via grantClaimsValidatedSchema.parse(claims) in the OAuth AS route. Issues that fail parse are rejected before the JWT is signed.
2. At tool-invocation time by @glideco/grant-wrapper — validates the decoded JWT payload before any tool handler runs.
3. Against the JSON Schema document for partner verification tooling:
   npx ajv-cli validate \
     -s https://glide.co/schemas/agent-banking/v1/scoped-grant-claims.json \
     -d ./my-grant.json
   

​

Common pitfalls

• Checking only aud.vault_id and ignoring aud.entity_id. A grant scoped to vault A within entity X is invalid against vault A re-assigned to entity Y. Both fields must match on every call.
• Issuing grants with TTL > 3600. grantClaimsSchema accepts longer-lived claims (it’s a structural schema); only grantClaimsValidatedSchema enforces the 60-min cap. The AS always uses the validated schema — custom AS implementations MUST replicate this check.
• Treating iss as required for backward compat. The iss field is optional at v1 so existing /draft/ consumers keep working. New AS implementations SHOULD set it.
• Using scope as a string. The Zod schema for scope is string[] (an array); the JSON Schema also defines it as an array. Some OAuth libraries serialize scope as a space-separated string. Parse the JWT payload before validating — decode-then-parse, not validate-raw-JWT-bytes.
• Using resource instead of aud for resource binding. The resource array is an optional RFC 8707 compatibility aid. Glide’s verifier derives canonical URIs from aud.vault_id + aud.entity_id, not from resource. Verifiers that only check resource leave tenant isolation unenforced.

​

Reading list

• OAuth flow — the full client_credentials → JWT → JWKS verify walkthrough.
• Grant — developer-facing explanation of what each claim means at runtime.
• AgentPolicyEnvelope — what policy_version references.
• Money-safety contracts — F3 + F5 IRON RULES the verifier enforces.
• Source on GitHub