Ask GeoScript

A natural-language interface that answers questions grounded strictly in a client's own observations, snapshots, and reports — never speculation.

For: Agencies, BusinessesCategory: measure

Private beta — available to agency partners

This capability is live and working for agencies in GeoScript's private beta program. Learn about agency access →

What Ask GeoScript does

Ask GeoScript is a natural-language Q&A interface for agencies to query their clients' data. An agency can ask questions like "which prompts is this client not appearing in?" or "what changed after the last deployment?" and receive answers grounded strictly in stored observations, snapshots, and reports. Ask GeoScript does not speculate, does not pull from external sources, and does not generate answers when no evidence exists — it refuses explicitly when data is insufficient.

How it works

Grounded in stored data only

Every answer Ask GeoScript produces is grounded in data stored in the client's workspace: observations, recommendations, deployment records, outcomes, and reports. GeoScript does not pull from external sources or from other clients' workspaces to answer a question. The context passed to the AI model is delimited to prevent prompt injection — an adversarial question cannot cause the model to access data it is not authorized to see.

Tenant isolation before retrieval

Before any retrieval step, Ask GeoScript enforces workspace isolation. Only data belonging to the agency's current workspace and the specific client context is eligible for retrieval. The isolation guard runs at the service layer. A question about Client A cannot surface data from Client B.

CostGate and deterministic zero-cost refusal

Every Ask GeoScript call passes through CostGate. If the workspace has no stored evidence — no observations, no recommendations, no outcomes — the system returns a deterministic refusal without making any AI API call. The refusal message is: "The available data doesn't show enough evidence to answer that question." No cost is incurred, and no speculation is produced.

Agency console only

Ask GeoScript is available in the agency console (app/app/ask). It is not available as a public-facing tool for clients or prospects. A public-docs version grounded in GeoScript's public documentation is a future feature, not yet built.

Live implementation

The current implementation uses a live Claude API call with a real cost, tenant isolation verified at the service layer, and 33/33 smoke tests passing including a live Claude API round-trip.

What Ask GeoScript does not do

Clear boundaries increase trust. These limitations are documented explicitly, not buried in footnotes.

Ask GeoScript does not speculate — it refuses to answer questions it cannot ground in stored data.
Ask GeoScript is not a general-purpose AI assistant — it only has access to the client's GeoScript workspace data.
Ask GeoScript is not available to clients or the public — it is an agency-console tool only.
Ask GeoScript cannot access real-time internet data, external databases, or AI engine internals.
The answers depend on the depth of stored data — a recently activated client with few observations will receive limited answers.

Reports — the snapshot data Ask GeoScript reads AI Visibility Monitoring — the observations it draws on Reporting — platform pillar Docs: Ask GeoScript

Other features

AI Visibility Monitoring

Private beta · 3 engines live

Run a client-specific prompt universe against multiple AI engines on a schedule, preserving each raw response as an immutable observation.

Outcome Measurement

Private beta

Compare AI observations from before and after each deployment inside a bounded time window to attribute visibility change to the intervention.

Reports