ConnectorManifest (draft)

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

Field	Type	Notes
`schemaVersion`	`'v1'`	Locks the manifest to v1 even while the doc is in `/draft/` channel.
`slug`	`string` (lowercase kebab-case)	Becomes the package directory name.
`displayName`	`string`	Human-readable name.
`vendor`	`string`	The vendor’s identifier. May differ from slug.
`trust`	`'community' \| 'verified' \| 'core'`	Quality-based trust tier.
`capabilities`	`Capability[]`	Array of declared capabilities (orchestration, kyc, card, screening, chain-receipt, balance, auth, banking, qr-gateway, oauth-authorization-server, attestation, merkle-anchor, timelock-module, recovery).
`regions`	`string[]`	ISO 3166-1 alpha-2 codes; or `*` for global.
`currencies`	`string[]`	ISO 4217 codes + crypto symbols.
`egressHosts`	`string[]`	Every host the connector touches at runtime. Enforced by the egress-host lint CI gate.
`compliance.jurisdictions`	`string[]`	Where the vendor is licensed.
`compliance.licenses`	`string[]`	Human-readable license names (“FinCEN MSB”, “BitLicense”, etc.).
`compliance.dataResidency`	`string[]`	Regions where the vendor stores customer PII.
`compliance.amlPosture`	`'vendor-screened' \| 'pass-through' \| 'unscreened'` (optional)	The connector’s AML posture.
`packageVersion`	`string`	Semver of the package.
`iconPath`	`string` (defaults `./icon.svg`)	Relative path to the package’s icon.
`isMock`	`boolean` (defaults `false`)	`true` for mock/fixture connectors.
`homepage`	`string` (URL, optional)	Vendor or package homepage.
`changelogUrl`	`string` (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:

At build time by Zod via ConnectorManifest.parse(manifest).
At PR time by scripts/validate-manifests.mjs (the connector-skill-ci CI gate).

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

Adding a connector — partner-PR flow.
License compatibility — what dependencies the manifest’s package.json can pull.

Overview AgentPolicyEnvelope (draft)

Get started

Concepts

Packages

Connectors

Agent skills

Headless MCP

Security

Standards

Legal

ConnectorManifest (draft)

Canonical URL

Required fields

Example

Validating against the schema

Relation to capability interfaces

Reading list

​Canonical URL

​Required fields

​Example

​Validating against the schema

​Relation to capability interfaces

​Reading list

Canonical URL

Required fields

Example

Validating against the schema

Relation to capability interfaces

Reading list