{"uid":"cap_EAmHqH9EoB_YrgrDuclBG","slug":"bolt-json-formatter-03850b05","name":"Bolt JSON Formatter","description":"Utility toolkit for AI agents. 54 endpoints — tools, data, and AI processing. Pay per request in USDC via x402.","url":"https://datault.orbonomy.xyz/api/json-format","method":"POST","headers":{},"bodySchema":{"type":"object","required":["json"],"properties":{"json":{"type":"string"},"indent":{"type":"integer"}}},"responseSchema":{"type":"object","properties":{"data":{"type":"object"},"success":{"type":"boolean"}}},"example":null,"exampleRequest":null,"tags":["x402"],"displayCostAmount":"0.01","displayCostAsset":"USDC","priceDynamic":false,"priceHint":null,"priceStatus":"priced","priceSource":"probe","requiresHandshake":false,"reviewCount":0,"rating":{"score":"0.00","successRate":"0.00","reviews":0,"stars":null,"state":"unrated"},"availabilityStatus":"unknown","priceObserved":null,"sessionDeposit":null,"pricing":{"kind":"static","summary":"$0.01/call","primary":{"kind":"static","protocol":"x402","network":"base","amountUsd":"0.01","per":"call","confidence":"exact"},"accepted":[{"kind":"static","protocol":"x402","network":"base","amountUsd":"0.01","per":"call","confidence":"exact"}]},"paymentMethods":[{"uid":"pm_ZOFuXZFKstl1bO2tZk_Fl","protocol":"x402","methodType":"crypto","chain":"base","mode":"charge","costAmount":"0.01","costPer":"request","priority":0,"asset":"0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913","unit":"request","depositMicros":null,"planRef":null}],"brandName":null,"brandSlug":null,"brandBaseUrl":null,"brandDocsUrl":null,"whatItDoes":"Formats and pretty-prints a JSON string with optional indentation control","exampleAgentPrompt":"Can you format this JSON string for me with 4 spaces of indentation so it's readable: '{\"name\":\"Alice\",\"age\":30,\"roles\":[\"admin\",\"user\"]}'?","exampleUseCases":[{"title":"Pretty-print API response for review","prompt":"I just got this ugly minified JSON back from an API call and need to read through it — can you pretty-print it with 2 spaces of indentation so I can actually make sense of it? Here it is: '{\"status\":\"ok\",\"data\":{\"id\":42,\"items\":[1,2,3],\"meta\":{\"page\":1,\"total\":100}}}'"},{"title":"Beautify JSON before logging","prompt":"Before we write this config payload to the logs, can you clean it up and format it nicely with 4 spaces so the team can read it easily? The raw string is: '{\"service\":\"auth\",\"env\":\"production\",\"flags\":{\"rateLimit\":true,\"debug\":false}}'"},{"title":"Normalize JSON for documentation","prompt":"I'm putting together some API documentation and need this JSON example to look clean and readable for developers — can you format it with standard indentation? Here's the raw string: '{\"endpoint\":\"/users\",\"method\":\"POST\",\"body\":{\"username\":\"jdoe\",\"email\":\"jdoe@example.com\"}}'"}],"resultDescription":"Returns a parsed JSON object under the 'data' key along with a boolean 'success' field indicating whether the formatting and parsing succeeded.","failureModes":["Invalid JSON string input causes parsing failure with success=false","Missing required 'json' field returns an error response","Malformed or truncated JSON string may result in a parse error","Negative or non-integer indent value may cause unexpected formatting"],"whenToPreferThis":"Use this endpoint when you have a raw JSON string that needs to be parsed into a structured object or pretty-printed with controlled indentation. Prefer this over manual parsing when working within the Bolt toolkit ecosystem and paying per-request via USDC x402.","instructions":null,"reviewSummary":null,"reviewSummaryHighlights":null,"reviewSummaryConcerns":null,"reviewSummaryGeneratedAt":null,"activationCount":0,"lastUsedAt":null,"lastSuccessfullyRanAt":null,"lastHealthCheckAt":"2026-09-14T00:47:21.405Z","isFirstParty":false}