Skip to main content

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.

The OSS connector manifest. Every package at packages/connectors/<slug>/ ships one of these as src/manifest.ts.

​
Canonical URL

https://glide.co/schemas/agent-banking/v1/connector-manifest.json

​
Required fields

FieldTypeNotes
schemaVersion'v1'Locks the manifest to v1 even while the doc is in /draft/ channel.
slugstring (lowercase kebab-case)Becomes the package directory name.
displayNamestringHuman-readable name.
vendorstringThe vendor’s identifier. May differ from slug.
trust'community' | 'verified' | 'core'Quality-based trust tier.
capabilitiesCapability[]Array of declared capabilities (orchestration, kyc, card, screening, chain-receipt, balance, auth, banking, qr-gateway, oauth-authorization-server, attestation, merkle-anchor, timelock-module, recovery).
regionsstring[]ISO 3166-1 alpha-2 codes; or * for global.
currenciesstring[]ISO 4217 codes + crypto symbols.
egressHostsstring[]Every host the connector touches at runtime. Enforced by the egress-host lint CI gate.
compliance.jurisdictionsstring[]Where the vendor is licensed.
compliance.licensesstring[]Human-readable license names (“FinCEN MSB”, “BitLicense”, etc.).
compliance.dataResidencystring[]Regions where the vendor stores customer PII.
compliance.amlPosture'vendor-screened' | 'pass-through' | 'unscreened' (optional)The connector’s AML posture.
packageVersionstringSemver of the package.
iconPathstring (defaults ./icon.svg)Relative path to the package’s icon.
isMockboolean (defaults false)true for mock/fixture connectors.
homepagestring (URL, optional)Vendor or package homepage.
changelogUrlstring (URL, optional)Where to read changelog entries.

​
Example

import { ConnectorManifest } from '@repo/connectors-base';

export const manifest = ConnectorManifest.parse({
  schemaVersion: 'v1',
  slug: 'my-vendor',
  displayName: 'My Vendor',
  vendor: 'my-vendor',
  trust: 'core',
  capabilities: ['orchestration', 'kyc'],
  regions: ['US', 'EU', 'GB'],
  currencies: ['USD', 'EUR', 'GBP', 'USDC'],
  egressHosts: ['api.my-vendor.com'],
  compliance: {
    jurisdictions: ['US', 'EU', 'GB'],
    licenses: ['My Vendor MSB'],
    dataResidency: ['US', 'EU'],
    amlPosture: 'vendor-screened',
  },
  packageVersion: '0.1.0',
});

​
Validating against the schema

The manifest is validated three ways:
  1. At build time by Zod via ConnectorManifest.parse(manifest).
  2. At PR time by scripts/validate-manifests.mjs (the connector-skill-ci CI gate).
  3. At publish time by the standards-implementer using the JSON Schema document directly: 
    npx ajv-cli validate \
  -s https://glide.co/schemas/agent-banking/v1/connector-manifest.json \
  -d ./my-manifest.json

​
Relation to capability interfaces

The capabilities array is the declaration; the actual TypeScript implementation lives at packages/connectors/_base/src/capabilities/<capability>.ts. The contract test suite (extending ContractTestSuite from @repo/connectors-base) asserts that each declared capability has a runtime implementation.

​
Reading list