Skip to main content

​
Phonefarm

Phonefarm is externally triggered phone execution infrastructure. TikTok is the default and most live-verified platform; capability requests are now platform-aware and can plan Instagram actions where the capability status allows it.

​
Who These Docs Are For

  • Teams integrating Phonefarm into another product or control plane.
  • Agents that need exact request and response contracts.
  • Engineers who need to understand process lifecycle, callbacks, idempotency, and capability constraints.

​
What Phonefarm Is

  • A process-oriented execution API.
  • A platform-aware capability runner for warmup, comment, posting, story, DM, account, maintenance, and support workflows.
  • A normalized process-status layer over richer internal queue and runtime mechanics.

​
What Phonefarm Is Not

  • Not a content generation system.
  • Not a scheduler that invents work on its own for external callers.
  • Not a public control plane for low-level worker internals.
  • Not yet a public workspace/resource-sync/semantic-operation API, even though the internal architecture foundation exists.

​
Official Integration Model

The primary public abstraction is the process API:
  1. Create work with POST /capability-requests/enqueue or POST /maintenance/requests.
  2. Receive process.updated callbacks on key milestones.
  3. Poll GET /processes/{process_id} for source-of-truth state.
  4. Cancel with POST /processes/{process_id}/cancel when needed.
Legacy queue-item posting endpoints still exist:
  • POST /ingest
  • POST /cancel
Those are compatibility endpoints for direct post-video queue items. New integrations should start with the process model.

​
Base URLs

  • Public API base URL: https://phonefarm.withmithras.com
  • Public docs base URL: https://docs.withmithras.com

​
Current Public Capabilities

See Capability Requests for the generated public capability list and per-capability routing table.

​
Important Caveats

  • TikTok fyp_warmup is live-verified for unattended watch-only use when like_probability, save_probability, and comment_probability are each explicitly 0.
  • Instagram keyword_warmup and fyp_warmup are manual-only until OnePlus live verification is complete.
  • fyp_comment_growth is manual-only and supports top-level comments only.
  • Callbacks are best-effort delivery. GET /processes/{process_id} is the source of truth.
  • Public statuses are normalized views over richer internal states.
  • Public timestamps are milestone-derived and should not be treated as precise device-action timestamps.
  • Target workspace keys, resource sync, semantic operations, and workflows are not public until they appear in these docs and openapi.json.