Jentic OSThe workplace. An in-house AI platform for every employeeJentic OneSafe access. Agents reach your systems without holding keysJentic AIRThe foundation. Gets your existing platforms ready for AI
Pricing

GET STARTED

API DirectoryBrowse 10,000+ APIs ready for AI agent integrationDocumentationGuides and API reference

TOOLS

API ScoringCheck your AI readiness using our scorecardArazzo UIVisualize Arazzo workflows as interactive documentationArazzo EditorBuild and edit multi-step API workflows visually

COMMUNITY

GitHubOpen source projects and examplesOpen StandardsBuilt on open specs. Never locked in.
All ResourcesEverything in one placeBlogLatest articles and insightsTech Talk NewsletterAPIs, AI agents, architecture and strategyWebinarsLive sessions and on-demand recordingsReports & WhitepapersOriginal research on enterprise AI
About UsOur mission and teamCareersJoin our teamContactGet in touch
Try it now
Jentic OSJentic OneJentic AIR
Pricing
API DirectoryDocumentationAPI ScoringArazzo UIArazzo EditorGitHubOpen Standards
All ResourcesBlogTech Talk NewsletterWebinarsReports & Whitepapers
About UsCareersContact
Try it now
JenticJentic
Products
  • Jentic OS
  • Jentic One
  • Jentic AIR
For Developers
  • API Directory
  • Documentation
  • GitHub
Company
  • About Jentic
  • Careers
  • Contact Us
  • Trust Centre
ISO/IEC 27001:2022 certification badge issued by Prescient SecurityISO/IEC 27001:2022 certification badge issued by Prescient Security

Information Security Management System

Certified to ISO/IEC 27001:2022 by Prescient Security

AICPA SOC for Service Organizations logoAICPA SOC for Service Organizations logo

SOC 2® Type 1 report

Audited by Prescient Assurance

Terms & Conditions•Privacy Policy•
© 2026 Jentic Technology Ltd. All rights reserved.
2 Grattan Court East, Dublin, D02 VX86, Ireland
Switch to light modeSwitch to dark mode
APIs / IOT / Google / SAS Portal API (Testing)
SAS Portal API (Testing) logo

Google SAS Portal API (Testing)

Browse all Google APIs
40
AI ReadinessFoundational (D-)40/100
See full scorecard
Official vendor OpenAPI document · agent-readyIOTDevice Managementoauth224 EndpointsREST

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.

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. It exposes operations for provisioning customer hierarchies, registering and validating CBSDs, signing devices, and managing deployment-level Google Cloud project bindings. The testing endpoint mirrors production semantics so integrators can exercise SAS workflows safely before promoting them to live spectrum operations.

Jentic One on GithubView OpenAPI Document

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.

1

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%2Fsas-portal-testing" | sh
2

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%2Fsas-portal-testing" | 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

Register, validate, and sign CBSD devices for CBRS deployments under a customer hierarchy

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

Generate and validate installer secrets for technicians commissioning CBRS radios

Get and set IAM-style policies that govern access to SAS resources

Run dry-run migrations and analytics setup for SAS customers ahead of production cutover

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

POST

/v1alpha1/policies:set

Set the access policy on a SAS resource

Jentic AI Readiness Score

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

S

SAS Portal API (Testing)

- Foundational (D-)
40/100
57
Foundational Compliance
56
Developer Experience & Jentic Compatibility
18
AI-Readiness & Agent Experience
94
Agent Usability
63
Security
56
AI Discoverability
Powered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
57

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: CSignals: 4
77%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

0%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

50%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

56

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: CSignals: 4
0%

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

25%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

18

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: FSignals: 4
74%

Description Coverage

Coverage of descriptions across API elements.

0%

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

0%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

0%

Summary Coverage

Coverage of summaries across operations/tags/info.

94

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1
94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

63

Security

Trust, risk posture, and security compliance.

Grade: B-Signals: 1
62%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

56

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: CSignals: 1
56%

Descriptive Richness

Clarity and depth of descriptions across API elements.

View full reportHow the score is calculatedMore about the dimensions

Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

Score your own APIScoring CLI agent skill
npx @jentic/api-scorecard-cli score <openapi-url>

Why Jentic?

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

Setup

Wiring the SAS Portal testing API by hand means configuring Google OAuth 2.0, minting scoped access tokens, and threading customer, deployment, and installer resource names through the v1alpha1 endpoints on prod-tt-sasportal.googleapis.com. Through Jentic you install once, import the SAS Portal testing API from the API Directory, store the OAuth credential once, and your agent calls it.

Permission scoping

This API carries the customer, deployment, and installer identifiers in the URL path, so a rule can pin your agent to one customer or deployment: it can provision and list within that scope and nothing else. You choose the operations it may call, so state-changing ones like migrating an organization or setting a policy 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 '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.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Identity and Access Management API

→

Manages the Google Cloud IAM identities that bind to SAS deployments

Use IAM to grant service accounts access to Google Cloud projects that back SAS deployments before calling SAS Portal endpoints.

Complementary

Cloud Key Management Service API

→

Stores and rotates the cryptographic keys used to sign SAS device certificates

Use Cloud KMS when you need HSM-backed key custody for SAS device signing instead of letting Google manage signing keys directly.

Complementary

Certificate Authority API

→

Issues private certificates used by CBSDs in custom PKI hierarchies

Use Certificate Authority Service when you need a private CA to issue device certificates outside Google's default SAS signing chain.

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.

GET STARTED

Start building with SAS Portal API (Testing) API

Explore with Jentic One
View OpenAPI Document