Google Pub/Sub Lite API

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

✓ Official Vendor SpecCloud InfrastructureServerlessoauth220 EndpointsREST

Install Jentic One Beta

Connect the Pub/Sub Lite API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Pub/Sub Lite 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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | 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 Pub/Sub Lite API.

Create and configure Pub/Sub Lite topics with explicit partition counts and per-partition throughput

Create subscriptions on a topic with delivery and backlog retention settings

Manage reservations to share throughput capacity across multiple topics

GET STARTED

Start building with Pub/Sub Lite API

Explore with Jentic

View OpenAPI Document

For Agents

Manage Google Cloud Pub/Sub Lite topics, subscriptions, reservations, and partition cursors for cost-efficient zonal streaming workloads.

Use for: I need to create a Pub/Sub Lite topic with 4 partitions, Inspect the consumer lag on a Pub/Sub Lite subscription, Create a reservation that shares throughput across multiple topics, Seek a subscription back to a specific publish timestamp

Not supported: Does not handle global multi-region messaging, push subscription delivery, or schema-validated topics - use for zonal partition-based streaming, capacity reservations, and cursor management only.

Use Cases

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

★ Cost-Efficient Log Ingestion

Pub/Sub Lite ingests application logs and telemetry at lower cost than Pub/Sub by trading global delivery for zonal partition-based throughput. Operators size partitions to expected throughput, attach subscriptions for downstream consumers, and use reservations to amortize capacity across topics.

Create a topic with 4 partitions and 4 MiB/s publish capacity per partition, then create a subscription named app-logs-archive for downstream archival.

Backlog Monitoring and Capacity Sizing

Operators monitor partition statistics and consumer lag to spot under-provisioned consumers and to decide when to scale partition counts. The topicStats and admin APIs expose backlog size and committed cursor positions per partition so dashboards can be built without polling consumers directly.

Compute backlog by partition for subscription telemetry-sub and alert when any partition has more than 60 seconds of unacked messages.

Replay and Reprocessing Pipelines

When a downstream consumer ships bad logic or a sink fails, operators rewind a Pub/Sub Lite subscription to a prior publish time and reprocess the affected window. The seek operation on the admin API issues this rewind without disturbing other subscriptions on the same topic.

Call seek on subscription orders-archive-sub with target publish_time set to one hour before the bad deploy to re-emit messages from that window.

Agent-Driven Streaming Operations

An ops agent uses Jentic to inspect Pub/Sub Lite lag, scale partitions, and trigger replays in response to alerts, so on-call engineers can resolve issues by describing intent rather than memorizing admin API paths.

Search Jentic for seek a pubsub lite subscription, load the schema for the admin seek operation, and execute it with the publish_time payload.

Key Endpoints

20 endpoints — google cloud pub/sub lite is a zonal, partition-based messaging service that offers lower per-message cost than pub/sub at the expense of zonal availability and explicit partition and capacity management.

METHOD

PATH

DESCRIPTION

GET

/v1/admin/{+parent}/topics

List Pub/Sub Lite topics under a parent

GET

/v1/admin/{+parent}/subscriptions

List subscriptions in a parent

GET

/v1/admin/{+parent}/reservations

List reservations in a parent

GET

/v1/admin/{+name}/partitions

Get partition information for a topic

POST

/v1/admin/{+name}:seek

Seek a subscription to a publish time or offset

POST

/v1/admin/{+name}:cancel

Cancel a long-running operation

GET

/v1/admin/{+parent}/topics

List Pub/Sub Lite topics under a parent

GET

/v1/admin/{+parent}/subscriptions

List subscriptions in a parent

GET

/v1/admin/{+parent}/reservations

List reservations in a parent

GET

/v1/admin/{+name}/partitions

Get partition information for a topic

POST

/v1/admin/{+name}:seek

Seek a subscription to a publish time or offset

Why Jentic?

Three things that make agents converge on Jentic-routed access.

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 'create a Pub/Sub Lite topic' or 'inspect partition lag', and Jentic returns the matching Pub/Sub Lite admin or topicStats operation with its input schema so the agent calls the right endpoint without parsing the discovery doc.

Time to first call

FAQs

Specific to using Pub/Sub Lite API through Jentic.

What authentication does the Pub/Sub Lite API use?

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

How is Pub/Sub Lite different from Pub/Sub?

Pub/Sub Lite is zonal and partition-based with explicitly provisioned throughput, which makes it cheaper but means topics live in a single zone and consumers must understand partitions. Pub/Sub is regional or global, autoscaled, and supports push subscriptions and schemas, but at higher per-message cost.

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

Throughput is governed by per-topic and per-partition publish and subscribe capacity, expressed in MiB/s, that you allocate at topic creation or via reservations. Admin API calls themselves are subject to standard Google Cloud project quotas.

How do I seek a subscription back in time through Jentic?

Search Jentic for seek a pubsub lite subscription, load the schema for the admin subscriptions seek operation which maps to POST /v1/admin/{+name}:seek, and execute it with a publish_time or starting offset payload.

Is the Pub/Sub Lite API free?

No, Pub/Sub Lite is billed by reserved publish and subscribe throughput per partition and by stored bytes. Pricing is published on the Google Cloud Pub/Sub Lite pricing page; you pay for capacity even when topics are idle, which is the trade-off for the lower per-message cost.

How do I see how far behind a consumer is?

Use the topicStats endpoints to fetch backlog size per partition and the cursor endpoints to see committed offsets. Subtracting committed offset from head offset gives a per-partition lag in messages.

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

Yes. Because your Jentic One instance is self-hosted, your own rules decide which Pub/Sub Lite operations and credentials the agent may use. Since the topic and subscription live in the URL path (/v1/admin/{+parent}/topics and /v1/admin/{+name}), you can pin the agent to a single topic or subscription and allow only read operations like listing topics or inspecting partition statistics. State-changing calls such as seeking a subscription (/v1/admin/{+name}:seek) or cancelling an operation stay out of scope unless you explicitly grant them.

Google Pub/Sub Lite API

Connect the Pub/Sub Lite API to your agent

Capabilities

Start building with Pub/Sub Lite API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs