decision-labs/geobase-skills/geobase-embeddings-rpc-applications

Applications: RPC API (Similarity + Change Detection)

When to use this skill

• Build app code calling similarity_search or change_detection
• Choose the correct RPC overload and parameters
• Embeddings tables already exist (creation is @geobase-embeddings-create-via-workers)

Use GeoEmbeddings RPC for embedding-native analysis after embeddings tables exist.

Required Inputs

• GEOBASE_PROJECT_URL
• GEOBASE_ANON_KEY
• table name(s) and optional label/filter inputs for your overload

Resolve URL/key from Studio / project settings during beta, or (when shipped):

geobase-cli projects env <project-ref> --persona web --format dotenv

See @geobase → Private beta (CLI not shipped).

Client Setup

JavaScript client should use geoembeddings schema:

import { createClient } from '@supabase/supabase-js'
const geobase = createClient(process.env.GEOBASE_PROJECT_URL!, process.env.GEOBASE_ANON_KEY!, {
  db: { schema: 'geoembeddings' },
})

Similarity Search (similarity_search)

PostgREST picks the PostgreSQL overload from the parameter names you send. Optional parameters (?) share defaults listed under Defaults and Behavior. The overload table below is the authoritative reference for agents using this skill (including change_detection). Public docs at docs.geobase.app are planned; until then, use this skill.

Examples below use the patch_id overload. For point/polygon/two-table calls, send the matching keys from the table (e.g. lon, lat, query_geometry, or table_name_1 + table_name_2).

Minimal JavaScript pattern:

const { data, error } = await geobase.rpc('similarity_search', {
  table_name: 'your_embeddings_table',
  patch_id: 1,
})
if (error) throw error

Raw HTTP pattern:

curl -sS -X POST "${GEOBASE_PROJECT_URL}/rest/v1/rpc/similarity_search" \
  -H "apikey: ${GEOBASE_ANON_KEY}" \
  -H "Authorization: Bearer ${GEOBASE_ANON_KEY}" \
  -H "Content-Type: application/json" \
  -H "Content-Profile: geoembeddings" \
  -H "Accept-Profile: geoembeddings" \
  -d '{"table_name":"your_embeddings_table","patch_id":1}'

Change Detection (change_detection)

Minimal JavaScript pattern:

const { data, error } = await geobase.rpc('change_detection', {
  table_name_1: 'baseline_embeddings_table',
  table_name_2: 'comparison_embeddings_table',
  similarity_threshold: 0.0,
})
if (error) throw error

Raw HTTP pattern:

curl -sS -X POST "${GEOBASE_PROJECT_URL}/rest/v1/rpc/change_detection" \
  -H "apikey: ${GEOBASE_ANON_KEY}" \
  -H "Authorization: Bearer ${GEOBASE_ANON_KEY}" \
  -H "Content-Type: application/json" \
  -H "Content-Profile: geoembeddings" \
  -H "Accept-Profile: geoembeddings" \
  -d '{"table_name_1":"baseline_embeddings_table","table_name_2":"comparison_embeddings_table"}'

Defaults and Behavior

• similarity_threshold default 0.0
• result_limit default NULL (no limit)
• result_offset default 0
• include_geom default false
• include_embeddings default false
• spatial_filter default NULL
• srid default 4326
• point overloads: radius default NULL, unit default 'm' ('m' or 'deg')
• change_detection returns change_score = 1 - similarity
• PostgREST selects overload by the exact parameter keys you send