cactuscompute.com valid

Cactus Compute

Cactus builds foundation models for on-device intelligence on any hardware: phones, wearables, automotive, laptops and microcontrollers. Deploy our models (Needle 3 for tool calling, Whistle for speech) or bring your own. Our hybrid models report a confidence score, so a request falls back to the cloud only when needed. This file is the index for agents: the Needle fine-tuning platform comes first, then the models themselves, then a pointer to the on-device SDK docs.

For agents: Cactus builds on-device foundation models (Needle for tool calling, Whistle for speech) with a fine-tuning platform, API reference, pricing and an on-device SDK

on-device aifoundation modelstool callingspeech modelfine-tuning

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-21T16:51:40.912Z. Cached copy · Source on cactuscompute.com

# Cactus Compute

> Cactus builds foundation models for on-device intelligence on any hardware: phones, wearables, automotive, laptops and microcontrollers. Deploy our models (Needle 3 for tool calling, Whistle for speech) or bring your own. Our hybrid models report a confidence score, so a request falls back to the cloud only when needed. This file is the index for agents: the Needle fine-tuning platform comes first, then the models themselves, then a pointer to the on-device SDK docs.

## What Cactus does

- Small models on everyday hardware: our smallest models run CPU-only on budget phones, wearables and Raspberry Pis, offline or hybrid, with no GPU, no server and no data leaving the device. Needle 3 and Whistle are open and in production, including in the Pebble app. See https://cactuscompute.com/needle and https://cactuscompute.com/blog/whistle.
- Your models, made smaller: we compress third-party foundation models as well as our own so they fit the memory of the device you ship. See https://cactuscompute.com/research.
- Hybrid routing: our models know when they are likely wrong and hand those requests to the cloud; everything else stays on the device. See https://cactuscompute.com/hybrid.

## Instructions for agents

You are probably here because a human asked you to make Needle handle their product's tools. Read this section, then the platform pages below, before calling anything.

What you can do with no key: read these docs, GET https://cactuscompute.com/v1/plans for hosted fine-tuning prices, and download the base model from https://cactuscompute.com/v1/models/needle-3/content to run it locally (see "Run and evaluate a model locally"). Do that first: if the base model already scores well enough on your human's test cases, there is nothing to pay for.

What needs your human: purchasing Starter or subscribing to Pro, and creating an API key. Explain which plan fits their use case and its limits, then link them to https://cactuscompute.com/dashboard/billing to pay themselves. Afterwards they create a key at https://cactuscompute.com/dashboard/api-keys and put it in the NEEDLE_API_KEY environment variable of the shell you run in. Never print the key, never paste it into a chat, and never write it into a file that is committed.

# Needle hosted fine-tuning pricing

These plans cover hosted fine-tuning in the Cactus console (https://cactuscompute.com/dashboard): data generation, training on our GPUs and evaluation. Downloading the base model and running any model locally is not billed.

Fine-tune locally for free, or use the platform for hosted GPUs, full-model training, a trained confidence head and 2-bit exports. Run your finished models on your own devices.

Free: $0 for local LoRA fine-tuning with the open-source package. Bring your own hardware and data; no hosted compute, generation or platform storage is included.

Start locally: https://github.com/cactus-compute/needle#customisation

Starter: $19 one-time for 3 fine-tunes, 3,000 gene
…

Related sites

Other listed sites in AI and machine learning. See the whole category →

Machine-readable: GET /v1/resolve?q=cactuscompute.com · GET /v1/domain/cactuscompute.com · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for cactuscompute.com:
1. POST https://agentwebmap.com/v1/sites/cactuscompute.com/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://cactuscompute.com/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/cactuscompute.com/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/cactuscompute.com).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.