Query over HTTP
Pull a nested value with a dot-path, index into an array, or filter an array of objects with eq / ne / gt / lt / like. Project one field out of the matches, or cast the result to text, number or bool.
Save a JSON document and get a URL. Read the whole file, or ask for just the field you need with a simple query string. Public or private, served from the edge.
Free plan, no card required · 1,000 requests/day · upgrade any time
One endpoint on api.jsonsilo.com/<uuid>. The query string picks one of four branches, checked top to bottom, and the first one that matches runs. No schema, nothing to set up.
Every read is the same GET. Which branch runs depends only on which params you send.
q / value / opFilter a top-level array. Add path= to project one field out of every match.
idxOne element of a top-level array, by position.
pathDot-path into the root document. A numeric segment indexes an array.
no paramsNothing to match, so the whole silo comes back.
Six comparisons, one per condition.
A three-item catalog, stored exactly as you posted it. Every example here reads from it.
[{ "name": "Notebook", "price": 6, "inStock": true,"tags": [{ "label": "paper" }, { "label": "sale" }] },{ "name": "Pen", "price": 2, "inStock": true,"tags": [{ "label": "ink" }] },{ "name": "Backpack", "price": 45, "inStock": false,"tags": [{ "label": "bags" }, { "label": "sale" }] }]
A filter is not limited to the element's own fields. Dots walk down into it.
Dot-separated keys. A numeric segment indexes an array.
Cast the value on the way out. Raw JSON by default.
Repeat the trio to AND them. Send the same number of each.
?q=price&value=5&op=gt
&q=price&value=50&op=lt
&path=name
["Notebook", "Backpack"]
Every plan includes the query engine, public and private silos, and edge caching. You're billed for capacity (silos, size and daily requests), not seats.
Perfect for trying it out.
For growing projects.
For serious workloads.
Need more than Pro? Talk to us.
Still stuck? The docs go deeper on every endpoint and operator.
A silo is one JSON file with its own web address. You save it once, then read all of it or just the parts you need over HTTP.
Only if you choose to make it public. New silos are private, so no one can read them without your key.
You send a key with each request. There's a read key for fetching data and a separate key for creating or changing silos from your own code.
Yes. You can reach a value deep inside the file, pick one item out of a list, or filter a list down to the items you want.
Each plan has a per-minute limit and a daily limit, from 1,000 requests a day on Free up to 10 million on Pro. Every response tells you how many requests you have left.
There's nothing to set up or connect to. You just read a file from a URL. It's made for config, content and small datasets, not for heavy transactional apps.
Germany, Singapore and the United States. Free silos stay in one region; Basic and Pro can pick any of the three.
Yes. Full reads are cached for about 30 minutes and query results for about 5, so busy endpoints stay fast. Saving a change clears the cache right away.
Sign up, paste some JSON, and copy the URL into your code. The Free plan is enough to ship something real.