Install Jentic One Beta

Connect the Cloud Pub/Sub API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Cloud Pub/Sub API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fgoogleapis.com%2Fcloud-pubsub" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fgoogleapis.com%2Fcloud-pubsub" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Cloud Pub/Sub API.

Create topics and configure message retention, schema, and ordering settings

Create push or pull subscriptions on a topic with custom ack deadlines and dead-letter policies

Publish batches of messages to a topic with attribute-based filtering metadata

GET STARTED

Start building with Cloud Pub/Sub API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Cloud Pub/Sub API for, with concrete tasks.

★ Event-Driven Microservices

Decouple producers and consumers across services using Pub/Sub as the asynchronous transport. Producers publish events to topics; consumers attach pull or push subscriptions, process messages, and acknowledge them. Pub/Sub handles delivery, retry, ordering, and dead-letter routing automatically across regions.

Create topic order-events with 7-day retention, create push subscription order-events-fulfillment to https://fulfillment.example.com/events, and publish a JSON message with attribute event_type=order.created.

Streaming Analytics Ingestion

Ingest high-volume application or device telemetry into Pub/Sub topics so downstream Dataflow or BigQuery pipelines can consume them in near real time. Schema validation can be enforced at the topic level so malformed events are rejected before they enter the pipeline.

Create a Pub/Sub schema in Avro, attach it to topic telemetry, then publish a batch of validated telemetry events from edge devices.

Disaster Recovery and Replay

Use Pub/Sub snapshots and seek-to-time to replay a subscription after a downstream consumer fails or after a bad deploy. Snapshots capture the unacked-message state, and seek operations rewind a subscription to a snapshot or wall-clock timestamp without affecting other subscriptions on the same topic.

Create a snapshot of subscription orders-fulfillment-sub, deploy the fix, then call seek with the snapshot name to redeliver messages from before the bad deploy.

Agent-Driven Event Publishing

An AI agent integrating with Google Cloud uses Jentic to publish events to Pub/Sub topics in response to user requests or upstream signals, so other workloads (workflows, analytics jobs, alerting) can react asynchronously without point-to-point integration.

Search Jentic for publish a message to a pubsub topic, load the schema for projects.topics.publish, and execute it with the topic and a base64-encoded message body.

Key Endpoints

33 endpoints — google cloud pub/sub is a globally distributed, fully managed messaging service for asynchronous service-to-service communication, event ingestion, and streaming analytics pipelines.

METHOD

PATH

DESCRIPTION

GET

/v1/{+project}/topics

List topics in a project

GET

/v1/{+project}/subscriptions

List subscriptions in a project

GET

/v1/{+project}/snapshots

List snapshots in a project

POST

/v1/{+name}:commit

Commit a schema revision

POST

/v1/{+name}:rollback

Rollback a schema to a prior revision

POST

/v1/{+parent}/schemas:validate

Validate a schema definition

POST

/v1/{+parent}/schemas:validateMessage

Validate a message against a schema

GET

/v1/{+project}/topics

List topics in a project

GET

/v1/{+project}/subscriptions

List subscriptions in a project

GET

/v1/{+project}/snapshots

List snapshots in a project

POST

/v1/{+name}:commit

Commit a schema revision

POST

/v1/{+name}:rollback

Rollback a schema to a prior revision

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the Cloud Pub/Sub API by hand means configuring Google OAuth 2.0 with the cloud-platform or pubsub scope, refreshing access tokens, and tracking topic, subscription, and snapshot resource names across every call to pubsub.googleapis.com. Through Jentic you install once, import the Cloud Pub/Sub API from the API Directory, store the OAuth credential once, and your agent calls it.

Permission scoping

This API puts the topic and subscription in the URL path (/v1/{+name} and /v1/{+project}/topics), so a rule can pin your agent to one topic or subscription: it can publish or pull there and nothing else. You choose the operations it may call, so state-changing ones like committing or rolling back a schema are not included unless you add them.

Credential isolation

Your Google OAuth credential is stored once, encrypted, by your own Jentic One instance and a scoped access token is injected at execution time. The credential never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'publish a message' or 'pull messages from a subscription', and Jentic returns the matching Pub/Sub operation with its input schema so the agent calls the right endpoint without reading Google's discovery doc.

FAQs

Specific to using Cloud Pub/Sub API through Jentic.

What authentication does the Cloud Pub/Sub API use?

The API uses Google OAuth 2.0 with the cloud-platform or pubsub scopes, sent as a Bearer token in the Authorization header. Through Jentic the OAuth credentials are stored in the vault and short-lived access tokens are minted per call so the refresh token never enters the agent.

Can I publish messages with attributes for filtering?

Yes, every message body can include a map of string attributes. Subscriptions can declare a filter expression that matches on those attributes, so the same topic can fan out to multiple consumers each receiving only the events relevant to them.

What are the rate limits for the Cloud Pub/Sub API?

Pub/Sub publisher and subscriber quotas are large by default and are documented on Google Cloud's Pub/Sub quotas page in MB/s and ops/s. For very high-throughput workloads consider using the gRPC client libraries instead of REST and request quota increases up front.

How do I publish a message through Jentic?

Search Jentic for publish a message to a pubsub topic, load the schema for the projects.topics.publish operation which maps to POST /v1/{+topic}:publish, then execute it with messages encoded as base64 in the request body.

Is the Cloud Pub/Sub API free?

Pub/Sub has a free tier of 10 GB of message data per month; beyond that, throughput is billed per GB ingested, delivered, and stored. Snapshots and seek operations also incur storage charges. Pricing is identical whether the API is called directly or through Jentic.

How do I replay messages after a bad deploy?

Take a snapshot of the subscription before the deploy with POST /v1/{+name}:createSnapshot semantics on snapshots, then call POST /v1/{+subscription}:seek with the snapshot name after the fix is deployed to redeliver messages that were acked during the broken window.

Can I limit what my agent is allowed to do with the Cloud Pub/Sub API?

Yes. Jentic One is self-hosted by you, so your own rules decide which Pub/Sub operations and credentials the agent may use. Because this API puts the topic and subscription in the URL path (for example /v1/{+project}/topics and /v1/{+name}), you can pin the agent to a single topic or subscription and let it only publish or pull messages there. You also choose which operations it can call, so state-changing ones like committing or rolling back a schema stay excluded unless you explicitly add them.

Google Cloud Pub/Sub API

Name: Cloud Pub/Sub API
Brand: Cloud Pub/Sub API
Availability: InStock

Browse all Google APIs

Official vendor OpenAPI document · agent-readyCloud InfrastructureServerlessoauth233 EndpointsREST

For Agents

Publish messages, manage topics and subscriptions, and pull or acknowledge messages on Google Cloud Pub/Sub for event-driven and streaming workloads.

Use for: I need to publish a message to a Pub/Sub topic, Pull pending messages from a subscription and acknowledge the ones we processed, Create a new topic with a 7-day message retention policy, Set up a push subscription that delivers messages to a Cloud Run service

Not supported: Does not handle long-running task scheduling, durable workflow orchestration, or stream processing transformations - use for asynchronous topic and subscription messaging only.

Google Cloud Pub/Sub is a globally distributed, fully managed messaging service for asynchronous service-to-service communication, event ingestion, and streaming analytics pipelines. The REST API exposes topics, subscriptions, snapshots, schemas, and IAM controls so producers can publish messages, subscribers can pull or acknowledge them, and operators can manage retention, ordering, and dead-letter behavior. Pub/Sub backs many Google Cloud event flows, including Cloud Storage notifications, Dataflow pipelines, and Cloud Run event triggers.

Jentic One on Github View OpenAPI Document

Connect the Cloud Pub/Sub API to your agent

Capabilities

Start building with Cloud Pub/Sub API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Google Cloud Pub/Sub API