SpaceBunny

SPACE BUNNY / FEATURE GUIDE

Get JSON output from Space Bunny Alpha

Choose JSON in the composer when the result needs to be a machine-readable object rather than a conversational explanation. It is useful for extracting fields from notes, organizing a checklist, or producing a compact record you can copy into another tool.

Open the free workspace ↗

How to use it

  1. Open the chat, click the response settings button beside the attachment controls, and enable JSON.
  2. Specify the fields, their intended types, and what should happen when a value is unknown. Supply the source text in the same message.
  3. Send the request. The app asks the provider for a JSON object and checks that the returned answer can be parsed before publishing it.
  4. Copy the object and validate it against your own application's schema before using it. A parseable object can still contain wrong values or missing fields.

Try this prompt

Extract a JSON object with fields "project" (string), "tasks" (array of strings), and "deadline" (string or null). Use null for an unknown deadline. Notes: Launch the landing page, review email delivery, and check mobile navigation.
Use this prompt in chat →

An example JSON structure

For the prompt above, this is an illustrative structure with the requested fields, not a recorded model response. Validate each field's type and content before passing it to another program.

{"project":"Launch the landing page","tasks":["Review email delivery","Check mobile navigation"],"deadline":null}

When it helps

For reliable extraction, explain how to handle uncertainty instead of asking the model to invent a missing value. Test downstream code with empty lists, null values and unexpected fields. Built-in tools can be enabled alongside JSON when arithmetic or a unit conversion is needed; their results still need a suitable output structure.

Limits and checks

Space Bunny supports response_format for JSON output without JSON Schema enforcement. This app checks JSON syntax and requires a top-level object; it does not guarantee field types, required properties or factual correctness. JSON and tool modes wait for the finished answer, so they do not display token-by-token output.

Keep exploring

Capability reference: OpenRouter ↗