The engine room behind SageWire.
SageWire is infrastructure for turning real-world activity into digital records and automated actions. The developer platform connects speech, location, weather, memory, onboarding, RFID, domain services, and field applications through reusable APIs.
This site is the technical view of SageWire: what is deployed, how the pieces connect, and which services are production, test, private, or still being built.
$ curl https://api.sagewire.dev/health
{
"service": "sagewire-api-gateway",
"status": "ok",
"version": "1.0"
}
Gateway greenlight confirmed.One gateway. Specialized services.
Applications and field devices stay focused on the job in front of the user. SageWire routes the specialized work to independent services behind a stable platform boundary.
Reusable infrastructure.
Core services provide the capabilities applications should not have to rebuild independently.
Gateway
Central API routing layer for SageWire applications and services.
Onboarding
Versioned onboarding flows, sessions, validation, completion state, persistence, and event-ledger auditing.
Speech-to-Text
Reusable transcription service for voice and field-capture workflows.
Location
Location enrichment and field context for events recorded outside the office.
Weather
Weather context by location, currently deployed at weather.herdmate.ag and used as a reusable enrichment service.
RAG
Retrieval and memory service for domain knowledge and application context.
EmberVox · TTS
Standalone text-to-speech capability for spoken replies and voice interfaces.
Software that reaches the physical world.
These services normalize hardware interaction so applications do not have to be written around one specific reader, indicator, or device.
RFID Service
Hardware-independent RFID infrastructure for UHF and future LF adapters, reader registration, reads, and field integrations.
RFID Test
Separate FastAPI migration/test deployment used to validate changes without treating test infrastructure as production.
Scale Service
Hardware-independent weighing infrastructure for raw readings, normalization, device registration, sessions, and usable weight events.
Specialists behind the applications.
These are service-layer specialists. Dave's Vet Station is the product layer that calls them according to animal type and workflow.
DAVE
Cattle and livestock specialist service used by Dave's Vet Station.
ALICE
Dogs and cats specialist service used by Dave's Vet Station.
JOE
Horse and equine specialist service used by Dave's Vet Station.
HAZEL
Exotics and small-animal specialist service used by Dave's Vet Station.
M.A.R.K. moves content through the pipeline.
M.A.R.K. is an AI-powered orchestration/API service, not an independent editorial intelligence. It routes field media through transcription, confidence checks, summarization/content generation, structured storage, and publishing outputs.
M.A.R.K.
Raw field video/audio → transcript → guardrail → summary/content → structured record → downstream publishing.
Where the platform meets actual work.
Not every application listed here was originally built on SageWire. This section deliberately distinguishes SageWire-native applications from connected or integrating products.
PTT Field Logger
A field-facing voice client that uses SageWire services for capture, transcription, context, and AI workflows.
Open headset app →Dave's Vet Station
Customer-facing veterinary guidance application that calls DAVE, ALICE, JOE, and HAZEL underneath the product experience.
Open Vet Station →HerdMate
Existing cattle-management platform originally built in AppSheet. It is increasingly integrating with SageWire services and field infrastructure; it is not presented here as originally built on SageWire.
Visit HerdMate →Scanner / RFID Tools
Field-facing RFID scanning and tag workflows connected to the broader SageWire hardware and record ecosystem.
Open scanner →Built around work outside the office.
Real field interfaces and context capture are part of the platform story—not decorative demos.
Field capture starts where the work is happening.
Audio, transcript, timestamps, and session history become durable artifacts.
Location and weather can travel with the event instead of being reconstructed later.
Production, test, and product endpoints.
The registry stays technical and usable: live browser checks, direct health tests, and copy-ready curl commands without forcing endpoint detail into the top of the page.
Production Services
api.sagewire.devonboarding.sagewire.devstt.sagewire.devloc.sagewire.devweather.herdmate.agrag.sagewire.devrfid.sagewire.devdave.sagewire.devalice.sagewire.devjoe.sagewire.devhazel.sagewire.devmark.sagewire.devApplications / Test
rfid-test.sagewire.devBrowser verification may be unavailable when a service does not allow cross-origin health requests. VERIFY does not mean DOWN. Use Test Health or Copy Curl for a definitive check. Internal infrastructure such as vector storage remains intentionally separate from the public service list.
MAP · OPS · SOP
The technical site is also the public map of how SageWire thinks about operating a service platform.
MAP
What exists: services, applications, domains, servers, owners, integrations, and endpoints.
OPS
What is happening: deployments, health checks, logs, runtime status, and service behavior.
SOP
How it gets built: repeatable playbooks for Docker, DNS, Coolify, testing, routing, and service creation.