Google SAS Portal API (Testing)

Name: SAS Portal API (Testing) API
Brand: SAS Portal API (Testing)
Availability: InStock

✓ Official Vendor SpecIOTDevice Managementoauth224 EndpointsREST

Install Jentic One Beta

Connect the SAS Portal API (Testing) to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the SAS Portal API (Testing), 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 SAS Portal API (Testing) API.

Provision and migrate SAS customers, including legacy organizations and Google Cloud project deployments

Manage SAS nodes and deployments to mirror real-world tower or campus topologies

GET STARTED

Start building with SAS Portal API (Testing) API

Explore with Jentic

View OpenAPI Document

For Agents

Manage CBRS Spectrum Access System deployments, devices, and customers in the Google SAS testing environment, including device signing and installer validation.

Use for: I need to register a new CBSD device in the SAS testing environment, Validate an installer secret for a field technician deploying a CBRS radio, Create a new SAS customer and bind it to a Google Cloud project deployment, List all deployments under a SAS customer to audit spectrum coverage

Not supported: Does not handle radio configuration, RF planning, or live production spectrum grants - use for Google SAS testing-environment customer, deployment, device, and installer management only.

Use Cases

Patterns agents use SAS Portal API (Testing) API for, with concrete tasks.

★ CBRS Deployment Staging

Use the testing SAS Portal to stage and rehearse CBRS deployments before promoting them to production. Operators can create representative customers, nodes, and devices, then exercise the full installer and validation flow without affecting live spectrum allocation.

Create a SAS customer, attach a deployment to a Google Cloud project, register a CBSD with serial number TEST-1234, and validate an installer secret end-to-end.

Installer Workflow Automation

Field installation of CBRS radios requires generating short-lived installer secrets and validating them when the technician registers the device on site. The SAS Portal API exposes both halves of this flow so it can be wired into work order systems.

Call /v1alpha1/installer:generateSecret, deliver the secret to the technician via SMS, then later call /v1alpha1/installer:validate when they confirm the device is on site.

Customer Onboarding and Migration

Onboarding a new SAS customer involves creating the customer record, provisioning a deployment bound to a Google Cloud project, optionally migrating from a legacy organization, and setting up analytics. The API exposes each of these steps as discrete operations so onboarding can be automated.

Create a new SAS customer for a wireless ISP, call customers:provisionDeployment to bind a Google Cloud project, then call customers:setupSasAnalytics to enable reporting.

Agent-Driven SAS Test Harness

An AI agent rehearses CBRS deployment scenarios in the SAS testing environment via Jentic, exercising customer creation, device registration, signing, and policy retrieval to validate that orchestration logic behaves correctly before pointing at production.

Search Jentic for register a CBSD device, load the schema, and execute a dry-run registration against the testing endpoint with synthetic device parameters.

Key Endpoints

24 endpoints — the sas portal api (testing) is the google spectrum access system staging surface used for managing cbrs (citizens broadband radio service) deployments, customers, nodes, devices, and installer workflows.

METHOD

PATH

DESCRIPTION

POST

/v1alpha1/customers:provisionDeployment

Provision a deployment for a customer

POST

/v1alpha1/customers:migrateOrganization

Migrate a legacy organization into the SAS hierarchy

POST

/v1alpha1/customers:setupSasAnalytics

Enable SAS analytics for a customer

POST

/v1alpha1/installer:generateSecret

Generate a short-lived installer secret

POST

/v1alpha1/installer:validate

Validate an installer secret on site

POST

/v1alpha1/policies:set

Set the access policy on a SAS resource

POST

/v1alpha1/customers:provisionDeployment

Provision a deployment for a customer

POST

/v1alpha1/customers:migrateOrganization

Migrate a legacy organization into the SAS hierarchy

POST

/v1alpha1/customers:setupSasAnalytics

Enable SAS analytics for a customer

POST

/v1alpha1/installer:generateSecret

Generate a short-lived installer secret

POST

/v1alpha1/installer:validate

Validate an installer secret on site

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 'provision a SAS deployment' or 'generate an installer secret', and Jentic returns the matching SAS Portal testing operation with its input schema so the agent calls the right endpoint without navigating the alpha discovery doc.

Time to first call

FAQs

Specific to using SAS Portal API (Testing) API through Jentic.

What authentication does the SAS Portal API (Testing) use?

The API uses Google OAuth 2.0 with the userinfo.email and SAS-specific scopes documented by Google. Through Jentic the OAuth credentials live in the vault and short-lived access tokens are injected into requests so the underlying client secret never reaches the agent.

Is this API safe to use against live spectrum?

No, this is the testing surface (prod-tt) and is intended for integration rehearsal only. Use it to validate registration, validation, and installer flows; switch to the production SAS Portal API endpoint when promoting code to live CBRS deployments.

How do I register a CBSD device through Jentic?

Search Jentic for register a CBSD device, load the schema for the SAS Portal customers.devices create operation under /v1alpha1/{+parent}/devices, and execute it with the device serial number, FCC ID, and installation parameters from your provisioning system.

What are the rate limits for the SAS Portal API?

Quotas are configured per Google Cloud project under the SAS Portal service. The testing endpoint is intended for low-volume integration work and does not guarantee production-level throughput, so batch heavy onboarding runs.

Can I migrate a legacy organization through this API?

Yes, call POST /v1alpha1/customers:listLegacyOrganizations to find candidates, then POST /v1alpha1/customers:migrateOrganization to migrate them into the SAS customer hierarchy. Run this against the testing endpoint first to confirm the resulting topology before touching production.

How do I validate an installer secret?

Generate the secret with POST /v1alpha1/installer:generateSecret, deliver it to the technician, then call POST /v1alpha1/installer:validate with the same secret on site to authorize the installation.

Can I limit what my agent is allowed to do with the SAS Portal API (Testing)?

Yes. Because you run Jentic One yourself, your own rules decide which SAS Portal operations and which OAuth credential the agent may use, and the customer, deployment, and installer identifiers travel in the URL path, so a rule can pin the agent to a single customer or deployment and let it only provision and list within that scope. You pick the operations it may call, so state-changing ones like customers:migrateOrganization or policies:set stay off limits unless you add them. That lets you allow safe read and registration flows such as customers.devices create or installer:validate while blocking anything that reshapes the SAS hierarchy.

Google SAS Portal API (Testing)

Connect the SAS Portal API (Testing) to your agent

Capabilities

Start building with SAS Portal API (Testing) API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs