JINN

A function for each task.

$ jinn run support-triage --prompt "Ticket #4812: charged twice" --in ./in
See the launch video 0:52
scroll
01 define

Write a function.

A function is one JSON file. It contains the instructions for its agent, the files that it receives and the files that it must make. You can add custom tools, setup commands, a machine size and a model. Jinn sets a value for each field that you do not set.

A function can also have no agent. Then your code controls each run with commands. Or create a persistent SSH machine that wakes when you connect and saves its disk when idle.

Publish the function with one command. Each time that you publish it, Jinn makes a new version. Each run records the version that it used.

function.json
{
  "name": "support-triage",
  "agent": {
    "system_prompt": "You answer billing tickets for Acme. /workspace/in contains the ticket (ticket.json) and the billing policy (policy.md). Find the customer with lookup_customer and the email address of the ticket. Obey all rules of the policy. Write the reply to the customer in /workspace/out/reply.md. Write the refunds to make in /workspace/out/actions.json, as a JSON array of {\"charge\": id, \"amount\": number, \"reason\": text}. If there are no refunds, write []. Write in ASD-STE100 Simplified Technical English. Then call complete.",
    "custom_tools": [{
      "name": "lookup_customer",
      "description": "Finds a customer by email address. Returns the plan, seats, prices and recent charges of the customer.",
      "parameters": { "type": "object", "properties": { "email": { "type": "string" } }, "required": ["email"], "additionalProperties": false },
      "url": "https://docs.usejinn.com/tools/lookup-customer",
      "secret": "sk_example_support"
    }]
  },
  "input_manifest": [
    { "path": "ticket.json", "description": "The ticket" },
    { "path": "policy.md", "description": "The billing policy" }
  ],
  "output_manifest": [
    { "path": "reply.md", "description": "The reply to send" },
    { "path": "actions.json", "description": "The refunds to make" }
  ]
}

$ jinn publish function.json
→ support-triage fnc_a3b59df3be29992f250c2e1e v1
02 run

Run it with a prompt.

Send a prompt and a folder from the CLI, or with one HTTP request. The function does the task. When the files in its output manifest are complete, Jinn sends them to you.

A webhook, a cron job, a form or your code can start a run. The CLI and the SDKs use the same API.

jinn


    
03 scale

Run it hundreds of times.

Each run starts clean. One run cannot change the work of a different run.

Start one run for each ticket, each pull request or each concept. There is no limit to the number of runs that you can start.

support-reply · 120 runs · 30× speed
$ ls tickets | xargs -P 10 -I{} \
    jinn run support-reply --prompt "Ticket {}" \
      --in tickets/{} --out replies/{}
04 pricing

A price for each minute of a run.

Each function has a size. If you do not set a size, the size is medium. The price of a size is $0.0625 for each GiB of memory, for each hour.

Jinn counts the time of a run from its start until it is complete. The time of setup is included. A minute that starts counts as a full minute. The tokens are on the bill from your model vendor, because the agent uses your key.

Read about pricing

s
Small 1 vCPU · 2 GiB · 24 GiB disk $0.125 for each hour · billed by the minute
m
Medium 2 vCPU · 4 GiB · 48 GiB disk $0.25 for each hour · billed by the minute
l
Large 4 vCPU · 8 GiB · 96 GiB disk $0.50 for each hour · billed by the minute
xl
X-Large 8 vCPU · 16 GiB · 192 GiB disk $1 for each hour · billed by the minute

Install the CLI.

Make an account with your email address. Your first account starts with $5 of credit. Then do the quickstart: publish a function and start a run.

$ curl -fsSL https://github.com/usejinn/jinn-cli/releases/latest/download/install.sh | sh