Pub/Sub Lite API

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

✓ Official Vendor SpecCloud InfrastructureServerlessoauth220 EndpointsREST

For Agents

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

Quickstart

Get started with Pub/Sub Lite API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"create a pubsub lite topic with partitions"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Pub/Sub Lite API 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

Inspect partition statistics, message backlog, and consumer lag for a topic

GET STARTED

Start building with Pub/Sub Lite API API

Explore with Jentic

View OpenAPI Document

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.

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. The admin API exposes topics, subscriptions, reservations, and partition statistics, while the cursor and topicStats APIs let consumers manage commit positions and inspect lag and throughput. Pub/Sub Lite is well suited for log ingestion, event archival, and telemetry pipelines that can tolerate zonal scope in exchange for predictable economics.

Use Cases

Patterns agents use Pub/Sub Lite API 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 though Jentic?

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

Credential isolation

Google OAuth 2.0 credentials are stored encrypted in the Jentic vault. Scoped, short-lived access tokens are issued per call so the OAuth client secret never enters the agent context, and IAM bindings on the project determine what admin and cursor operations the agent can perform.

Intent-based discovery

Agents search Jentic by intent (e.g., create a topic, seek a subscription, inspect lag) and Jentic returns the matching Pub/Sub Lite admin or topicStats operation with its input schema so the agent can build a correct request without parsing the discovery doc.

Time to first call

Direct integration takes 2-3 days because partition sizing, reservations, and cursor semantics need to be modelled correctly. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Cloud Pub/Sub API

Globally distributed, autoscaled messaging service with push subscriptions and schemas

Choose Pub/Sub when you need global delivery, push subscriptions, or schema enforcement; choose Pub/Sub Lite when cost predictability and partition control matter more than global reach.

Complementary

Cloud Dataflow API

Stream and batch processing engine that consumes Pub/Sub Lite topics

Use Dataflow when Pub/Sub Lite messages need real-time transformation into BigQuery, GCS, or other downstream sinks.

Complementary

BigQuery API

Analytics warehouse that ingests Pub/Sub Lite-derived event streams

Use BigQuery as the analytical sink for Pub/Sub Lite topics when downstream consumers need SQL access to event data.

FAQs

Specific to using Pub/Sub Lite API 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.