TERRA avatar

TERRA

Official

@tryterra · United Kingdom

0Followers
|
52Public Repos
|
9Published Skills

API that makes it easy to access dynamic health data from wearables and sensors

Skills Distribution
DomainData Systems...Wearable Health Da.. (35%)Clinical Diagnosti.. (25%)Real-Time Biometri.. (15%)Mobile Health SDKs (15%)

Agent Skills by TERRA

Showing 9 vetted skills indexed across 1 GitHub repositories.

Frequently Asked Questions About TERRA

FAQPage Schema
What tasks can I build using Terra's skills?

You can unify health data from 500+ wearables, order at-home or lab diagnostics with FHIR results, parse lab report PDFs into LOINC-coded biomarkers, stream live biometrics over websockets, push GPS routes and structured workouts to Garmin, COROS, and Wahoo devices, and run sleep or menstrual-cycle models.

Who are Terra's skills designed for?

They target health-tech and fitness developers building apps on wearable data, digital-health teams integrating diagnostic test ordering, and engineers needing real-time biometric streams or on-device Apple Health, Samsung Health, and Health Connect connections via TerraiOS, TerraAndroid, React Native, or Flutter bridges.

How do I install and run the Terra CLI?

Install via Homebrew with brew install tryterra/tap/terra or npm with npm install -g @tryterra/cli. Once on PATH, it reads and changes account configuration—environments, providers, webhook destinations, API keys, users, and billing—and can resend missed webhook events or test data requests directly.

Are Terra's skills open source and what do they cost?

All nine skills are released under the MIT license and are free to use and modify. However, the underlying Terra platform is a commercial service: features like model runs carry model_run pricing, and Vantage diagnostics requires manual partner onboarding before ordering tests.

What prerequisites and dependencies do Terra's skills require?

Most skills require network access to docs.tryterra.co for endpoint schemas and payload examples. Authentication uses a Terra dev-id and API key via HTTP Basic or headers, with HMAC signature verification for webhooks. The CLI additionally requires the terra binary installed via Homebrew or npm.