@pleach/transport-vertex
First-party Google Vertex AI transport for cloud-routed Pleach runtimes — workload-identity credentials, region pinning, and Vertex-specific cost-event emission.
Not yet published. @pleach/transport-vertex is marked private
in this monorepo and is not on npm — npm install @pleach/transport-vertex
will not resolve today. This page documents the planned surface; the
package publishes in a later cut.
@pleach/transport-vertex is the Google Vertex AI route for a
Pleach session whose buyer reaches Anthropic, Google, or other
Vertex-hosted families through their GCP project. It implements
the AgentProvider interface from @pleach/core against the
Vertex AI API, so cascade behavior and audit shape stay
consistent with every other provider — only the transport and
the credential binding change.
What it provides
- An
AgentProviderimplementation against the Vertex AI API per thecloud-routed-agent.mdxtransport-vs-family split. - Workload-identity credential resolution — pod-bound,
short-lived tokens from the GCP identity layer, per the
IAM-federated credentials section of
cloud-routed-agent.mdx. - Region pinning at the endpoint URL, enforced by Vertex rather
than the runtime (
cloud-routed-agent.mdx: region as a hard constraint). - Vertex-specific cost-event emission so the
harness_auditable_callsrow carries the cloud, region, and model dimensions GCP billing rolls up by — same reconciliation shape as the Bedrock route, against a different invoice.
Where it fits
@pleach/transport-vertex plugs into the same provider slot
on SessionRuntime that the direct-API providers fill — it
satisfies the AgentProvider contract documented in
Providers. For the architectural shape of a
Vertex-routed deployment — transport vs family, IAM federation,
region as a hard constraint, cost reconciliation — see
Cloud-routed agent.
Install
npm install @pleach/transport-vertexAPI surface
The provider factory signature, the workload-identity option
shape, the region and project fields, and the emitted cost-event
payload all live on the package's npm page:
@pleach/transport-vertex.
This page is placement orientation — what the SKU is for and
where it slots into the substrate. The npm README is the source
of truth for the constructor and option shapes; if a claim here
disagrees with the published README, the README wins.
Where to go next
Cloud-routed agent
Transport-vs-family, IAM federation, region pinning, and cost reconciliation to the cloud invoice.
Providers
The AgentProvider contract this transport implements and the cascade rules it threads through.
Region-pinned agent
The sibling shape when family + region pinning is procurement-driven rather than cloud-driven.
@pleach/transport-bedrock
First-party AWS Bedrock transport for cloud-routed Pleach runtimes — STS-federated credentials, region pinning, and Bedrock-specific cost-event emission.
Architecture
The substrate view of @pleach/core — six pieces, one stage lattice, and the boundary rules CI enforces. Each piece links to its deep-dive page.