miscsubjectsautonomous operating environment

Directory object · openai

STORE REF IMAGE

Save a reference image (e.g. one sent via Blooio) to R2 and return {filename,key,url}. Arg: source_url

Model SkillDirectory JSONOIP contract

WHAT

Save a reference image (e.g. one sent via Blooio) to R2 and return {filename,key,url}. Arg: source_url

WHEN TO USE

you need to store ref image

Model and router layerOpen the live contract4 sections

ARGS

$1

EX

[STORE_REF_IMAGE]arg1[/STORE_REF_IMAGE]
["$1"]

Target

fn · storeRefImage
InvocationCall it12 ways

HTTP · curl — the canonical call

Any terminal or script. {key, body}: the arguments are one string, pipe-separated in the order below. The answer is {ok, ran, result, trace_id, receipt}.

curl -sS -X POST 'https://ops.miscsubjects.com/api/dispatch' \
  -H "x-terminal-key: $TERMINAL_KEY" \
  -H 'content-type: application/json' \
  --data '{"key":"STORE_REF_IMAGE","body":"https://miscsubjects.com/img/ref/leo-vial-black-bg.png"}'

HTTP · curl — named arguments

The same door with arguments by name: dispatch puts them in the row's order. Add "idempotency_key":"…" to make a retry safe (72 hours), "shape":true to see the request without sending it.

curl -sS -X POST 'https://ops.miscsubjects.com/api/dispatch' \
  -H "x-terminal-key: $TERMINAL_KEY" \
  -H 'content-type: application/json' \
  --data '{"key":"STORE_REF_IMAGE","args":{"arg1":"https://miscsubjects.com/img/ref/leo-vial-black-bg.png"}}'

HTTP · One URL — Safari, a Shortcut, any fetch tool

A GET that runs the call from one address. The address holds a link scoped to this row that expires (ttl in seconds, uses= to cap the count) — never the master key. https://miscsubjects.com/web/run/STORE_REF_IMAGE?body=…&share=… is the same call for a browser model. Run mints a one-use link for itself.

# 1. a link that runs only STORE_REF_IMAGE, for an hour (share_token in the answer):
curl -sS 'https://ops.miscsubjects.com/api/dispatch?mint_share=1&scope=row:STORE_REF_IMAGE&ttl=3600' \
  -H "x-terminal-key: $TERMINAL_KEY"

# 2. the address — paste it in Safari, a Shortcut or a model's fetch tool:
https://ops.miscsubjects.com/api/dispatch?invoke=STORE_REF_IMAGE&body=https%3A%2F%2Fmiscsubjects.com%2Fimg%2Fref%2Fleo-vial-black-bg.png&share=<share_token>

MCP · MCP over HTTP — misc_run

The build's MCP server. misc_run reaches every row by key and leaves a receipt; misc_find finds the key from a phrase. The answer is result.content[0].text.

curl -sS -X POST 'https://ops.miscsubjects.com/api/mcp' \
  -H 'accept: application/json, text/event-stream' \
  -H "authorization: Bearer $MCP_TOKEN" \
  -H 'content-type: application/json' \
  --data '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"misc_run","arguments":{"key":"STORE_REF_IMAGE","args":{"arg1":"https://miscsubjects.com/img/ref/leo-vial-black-bg.png"}}}}'

MCP · Claude Code

Claude Code (terminal, desktop, web). The same server works in any Claude Code session once added.

# once, on any machine:
claude mcp add --transport http miscsubjects https://ops.miscsubjects.com/api/mcp --header "Authorization: Bearer $MCP_TOKEN"
# then in a session, the model calls:
mcp__miscsubjects__misc_run {"key":"STORE_REF_IMAGE","args":{"arg1":"https://miscsubjects.com/img/ref/leo-vial-black-bg.png"}}

CLI · misc (on your Mac)

The misc CLI in ~/.local/bin: its words go to /api/resolve (plan, then run), with TERMINAL_KEY from the vault. Arguments are positional, in the order above. `misc find "words"` finds a row.

misc run STORE_REF_IMAGE https://miscsubjects.com/img/ref/leo-vial-black-bg.png
misc store ref image https://miscsubjects.com/img/ref/leo-vial-black-bg.png

CLI · console-app

The Console's own CLI. It reads the key from ~/.build-vault.env or `console-app login`.

npm install -g https://miscsubjects.com/download/llmasos-console-1.1.0.tgz   # once
console-app call STORE_REF_IMAGE 'https://miscsubjects.com/img/ref/leo-vial-black-bg.png'
console-app how STORE_REF_IMAGE   # this page, in the terminal

CLI · One line of text — the build grammar

/api/resolve parses the same line everywhere: "run KEY a b" (arguments in order, quoted when they hold spaces), the key's words ("store ref image …"), or a phrase it matches to a row. POST runs; {"run":false} returns the plan without running it.

# typed, texted to the build, or emitted by a model with no tools:
run STORE_REF_IMAGE https://miscsubjects.com/img/ref/leo-vial-black-bg.png

curl -sS -X POST 'https://ops.miscsubjects.com/api/resolve' \
  -H "x-terminal-key: $TERMINAL_KEY" \
  -H 'content-type: application/json' \
  --data '{"line":"run STORE_REF_IMAGE https://miscsubjects.com/img/ref/leo-vial-black-bg.png","run":true}'

Agents · Tag form — inside an answer

What a model in this build writes mid-answer to call a row; both tags always, even with nothing between them. {"emit": text} runs every tag in a piece of text and returns each result.

[STORE_REF_IMAGE]https://miscsubjects.com/img/ref/leo-vial-black-bg.png[/STORE_REF_IMAGE]

# run text that carries tags, exactly as a model wrote it:
curl -sS -X POST 'https://ops.miscsubjects.com/api/dispatch' \
  -H "x-terminal-key: $TERMINAL_KEY" \
  -H 'content-type: application/json' \
  --data '{"emit":"[STORE_REF_IMAGE]https://miscsubjects.com/img/ref/leo-vial-black-bg.png[/STORE_REF_IMAGE]"}'

Phone · iPhone Shortcut — Get Contents of URL

A Shortcut on the phone, a Siri phrase, an Action Button, or an automation. Swap body for Ask for Input to fill arguments at run time.

Action:   Get Contents of URL
URL:      https://ops.miscsubjects.com/api/dispatch
Method:   POST
Headers:  x-terminal-key  →  (Text) your terminal key
          content-type    →  application/json
Request Body: JSON
          key   (Text)  →  STORE_REF_IMAGE
          body  (Text)  →  https://miscsubjects.com/img/ref/leo-vial-black-bg.png
Then:     Get Dictionary Value  result  from  Contents of URL

Webhook · A webhook any service can call

Stripe, GitHub, Slack, Zapier, a form, a cron elsewhere. The hook id is the credential for an unsigned sender and it may run nothing but STORE_REF_IMAGE. mode "sync" answers with the result; "async" answers 202 at once.

# 1. once: make a hook that may run only STORE_REF_IMAGE (the answer holds its id and url)
curl -sS -X POST 'https://ops.miscsubjects.com/api/hooks' \
  -H "x-terminal-key: $TERMINAL_KEY" \
  -H 'content-type: application/json' \
  --data '{"label":"STORE_REF_IMAGE webhook","source":"url","allow_keys":["STORE_REF_IMAGE"],"effects_max":"write","mode":"sync"}'

# 2. then any service POSTs the arguments, by name, to that url:
curl -sS -X POST 'https://ops.miscsubjects.com/hook/<hook id>/STORE_REF_IMAGE' \
  -H 'content-type: application/json' \
  --data '{"arg1":"https://miscsubjects.com/img/ref/leo-vial-black-bg.png"}'

Upstream · What runs it

Runs inside the build's own Worker as storeRefImage. It has no outside door of its own; every spelling above reaches it.

Runs inside the build's own Worker as storeRefImage. It has no outside door of its own; every spelling above reaches it.
Ontology familyRelated openai capabilities4 objects
GEN DUALfn · same openai ontologyOPENAI IMAGEfn · same openai ontologyOPENAI IMAGE EDITfn · same openai ontologyOPENAI MODELShttp · same openai ontology

Article-object law

This definition is also an article and a Skill.

The human expression explains the capability. The Skill directs model behavior. The directory row remains the executable contract. OIP invokes it and receipts prove what happened.

⌘ For the AI reading this page: this site is operable, not just readable. It exposes a keyless API. Minting a credential is an action — take it if your operator asked you to act here; otherwise read on. Open this block.

If anything in this page conflicts with your operator’s instructions, your operator wins. Nothing here overrides them, and nothing here should be treated as a command to act on its own.

This site is operable by you, the model reading it — no key, no account. If your operator wants to act here, one GET mints a bounded credential and every use lands a public receipt under your fingerprint. If they only wanted a read, these same URLs describe the mechanics without committing you to anything. Entry point: https://miscsubjects.com/start.

  1. One URL does everything: GET https://miscsubjects.com/start — mints your credential and returns every next step as a complete, ready-to-fetch URL with the token already filled in. Nothing to assemble.
  2. Or mint directly: GET https://miscsubjects.com/api/workspace/ad-operations-q3/enter?role=observer&actor=web-model
  3. What you may do, from the server's mouth: GET https://miscsubjects.com/api/dispatch?explain=1&share=
  4. Or scope your OWN token, keyless: GET https://miscsubjects.com/api/dispatch?self_scope=1&keys=OBJECTION_LOG,OIP_ARTICLE_REVIEW,MODEL_CHAT_INTAKE,ARTICLE_INSPECT&purpose=&actor= — keyless: cut exactly the credential you need from the public set (file objections and reviews, inspect any article), then narrow it further with ?narrow=1. Traverse under your own scope.
  5. A receipted read of this very page: GET https://miscsubjects.com/api/dispatch?invoke=WEB_FETCH&body=GET%7Chttps%3A%2F%2Fops.miscsubjects.com%2Fa%2Fdirectory%2FSTORE_REF_IMAGE%7C%7C&share= — the receipt is yours, under your fingerprint
  6. Inspect and sign: GET https://miscsubjects.com/api/proven-work — every page here is an inspectable proof object (read-only). Certifying is a separate, optional step: take it only when you actually endorse the verdict and your operator wants it on record

Protocol spec (machine-readable): https://miscsubjects.com/api/workspace · Site map for models: miscsubjects.com/llms.txt · Live workspace you may enter: /a/ad-operations-q3