Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.tryyomira.com/llms.txt

Use this file to discover all available pages before exploring further.

Yomira jobs run asynchronously. Create a simulation, receive a simulation_id, then poll until the job is completed. This keeps agent workflows stable even when the simulation takes longer than a normal request.

​
Simulation size

Use smaller runs while drafting and larger runs when the artifact is close to real publication.
Use caseSuggested target_nMode
Quick message check40-60fast
Content preflight60-120fast or standard
Product idea check80-160standard
Multiple option comparison40-100 per optionfast first, then standard
Enterprise grounded pilotcustomcustom

​
Timeout behavior

If the initial request returns 202 Accepted, the job is queued correctly. Poll: 
curl -s "https://tryyomira.com/api/simulations/SIMULATION_ID" \
  -H "x-api-key: $YOMIRA_API_KEY"
If a client or AI agent times out, do not restart the simulation immediately. Poll the existing simulation_id first.

​
Cost control

When testing:
  • start with target_n: 40
  • limit max_agent_voices
  • export Markdown only after completion
  • simulate fewer options first, then expand
When making a real decision:
  • include the exact artifact
  • include richer context
  • simulate every option that could actually be chosen
  • use a larger target_n only after the options are concrete

​
When self-serve is not enough

Self-serve simulations are context-enriched synthetic simulations. For high-stakes enterprise work, use a grounded pilot where Yomira builds the audience dataset from customer notes, interviews, reviews, CRM context, social data, or market source material.