GeoStream AI

GEOSTREAM AI / CODING AGENTS

Give your coding agent
the right context.

Use Codex, Claude Code or another coding agent to create and run a small local GeoStream app. The agent reads the contract, discovers live capabilities, and makes API calls from its local server—not from the browser.

HOW TO USE A CODING AGENT

Capabilities first.
Run locally second.

Copy an example into Codex, Claude Code or a similar agent. It should use live capability data, create the local app, start it and package the result—without inventing data or exposing credentials.

01 / READ

OpenAPI + AIContract

Descriptions declare input locations, type rules, joins and security behaviour.

02 / DISCOVER

GetCapabilities

Capabilities expose the current published workspaces, resources, operations and formats.

03 / CREATE

Code with AI

Give the prompt to your coding agent and let it create the application from the live API contract and capabilities.

SERVICE EXAMPLES

Prompts for
coding agents.

Use these prompts in Codex, Claude Code, Cursor or a similar coding agent. The agent can run API work in its local environment; a downloaded HTML file calling the API directly still depends on public CORS support.

01 / METRICS

Operational health

Build a compact status view from the Prometheus-compatible endpoint.

OpenAPI: https://product-api.geostream-ai.com/openapi/v1.json
Create one standalone index.html for GeoStream Metrics. Parse metrics and show health.
02 / XYZ

XYZ tile map

Discover a public layer and render its published URL template.

OpenAPI: https://product-api.geostream-ai.com/openapi/v1.json
Create a standalone index.html for GeoStream XYZService. Use AIContract and GetCapabilities; allow the user to select a public layer, then display the selected layer in OpenLayers at its correct geographic location and zoom to it. Use 256×256 tiles and OpenStreetMap as the basemap. Do not modify or encode URLs. Use the GetCapabilities; do not build them manually. Make sure the HTML works directly in a normal web browser.
03 / WFS

Feature explorer

Read OGC capabilities, schema and a selected feature type.

OpenAPI: https://product-api.geostream-ai.com/openapi/v1.json

Create a standalone index.html for GeoStream WFS. Read AIContract, retrieve GetCapabilities, and use them to build the interface. Allow the user to select a layer and create an interface where I can try all methods and their parameters. Display the results in a text box. Percent-encode all query parameter values. Use the GetCapabilities; do not build them manually.
04 / WMTS

Matrix-aware tiles

Use published layer, style, format and matrix values.

OpenAPI: https://product-api.geostream-ai.com/openapi/v1.json
Create a standalone index.html for GeoStream WMTS. Use AIContract and GetCapabilities; allow the user to select a public layer, then display the selected layer in OpenLayers at its correct geographic location and zoom to it. Use 256×256 tiles and OpenStreetMap as the basemap. Do not modify or encode URLs. Use the GetCapabilities; do not build them manually. Make sure the HTML works directly in a normal web browser.
05 / TABLE SERVICE

Published data reader

Resolve an item to a table and use only GetTable.

OpenAPI: https://product-api.geostream-ai.com/openapi/v1.json
Create a standalone index.html for GeoStream TableService. Read AIContract, retrieve GetCapabilities, and use them to build the interface. Allow the user to select a layer and create an interface where I can try all methods and their parameters. Display the results in a text box. Use the GetCapabilities; do not build them manually.
06 / WMS

Rendered map & identify

Use capabilities to form valid GetMap and GetFeatureInfo calls.

OpenAPI: https://product-api.geostream-ai.com/openapi/v1.json
Create a standalone index.html for GeoStream WMS. Use AIContract and GetCapabilities; allow the user to select a public layer, then display the selected layer in OpenLayers at its correct geographic location and zoom to it. Use 256×256 tiles and OpenStreetMap as the basemap. Do not modify or encode URLs. Use the GetCapabilities; do not build them manually. Make sure the HTML works directly in a normal web browser.
07 / ASSET SERVICE

3D asset browser

Choose a published asset and handle its capability type.

OpenAPI: https://product-api.geostream-ai.com/openapi/v1.json
Create a standalone index.html for GeoStream AssetService. Read AIContract, retrieve GetCapabilities, and use them to build the interface. Allow the user to select a public layer, then display it in Cesium. Use ArcGIS World Imagery as the basemap. Display the selected data at its actual geographic location and zoom to it. If a GLB does not have a valid geographic location or its location cannot be determined, place it in London and zoom to it; do not assume that boundingSphere information is always available. For terrain data, focus on Türkiye. Use the GetCapabilities; do not build them manually.
08 / AI SERVICE

AI layer client

Render only inputs and outputs advertised by a layer capability.

OpenAPI: https://product-api.geostream-ai.com/openapi/v1.json
Create a standalone index.html for GeoStream AIService. Read the AIContract, retrieve GetCapabilities, and build the interface accordingly. Let the user select a public AI layer and chat with it. Display the AI responses in the chat interface. If GetCapabilities defines file or image input, allow file uploads. Do not modify or encode URLs.

READY TO USE GEOSTREAM WITH AI

Use the contract as context.
Let AI guide the integration.