outputcharts

Dashboards that run on JSON

[outputcharts @outputcharts]

@Japheth_studio Painfully true. Two habits that help: map client spellings to one key before grouping, and turn "N/A" into null, not 0, so averages don't sink. Once the rows are clean, a chart is just {"xKey":"week","series":[...],"data":[...]}. https://t.co/PALpd782o5 draws that part.

[outputcharts @outputcharts]

@mordechaihoff @blurrdgoods The limit vanishes when Claude rebuilds the UI every time. Cheaper split: have it write one script that pulls Ads/Shopify/inventory on a cron and PUTs the numbers as JSON. The page never gets regenerated. That's the idea behind https://t.co/PALpd77uyx, one JSON doc per chart.

[outputcharts @outputcharts]

@chriszeuch Because the reports are prose and you want the numbers. Have the bot end each run with one PUT:

curl -X PUT $url -H "Authorization: Bearer $KEY" -d '{"label":"Leads found","value":7,"format":"number"}'

That's a KPI tile on https://t.co/PALpd77uyx. Self-awareness optional.

[outputcharts @outputcharts]

@paulopierrondi The weekly numbers nobody wants to assemble: signups, MRR, churn. The agent works them out, PUTs JSON to an Output Charts dashboard, and the team opens the same link every Monday. No data connector, only the final numbers leave your side.

[outputcharts @outputcharts]

cURL is fine for trying things out. To push on a schedule, run the same request from a script, a cron job, or a CI step. Create a free account to build the dashboard first; upgrading to Solo turns on API keys.

[outputcharts @outputcharts]

https://t.co/SpueiJYbpg

[outputcharts @outputcharts]

Your dashboard shouldn't need you to paste numbers in every morning.

New guide: update a live chart with one cURL command. Make an API key, copy the chart's push URL, send JSON. Done.

See below.

[outputcharts @outputcharts]

@gabrielrosinol @AnthropicAI The even-pace line is the whole trick. To get it outside Claude, that hourly JSON maps straight to a line chart:

{"xKey":"at","series":[{"key":"used"},{"key":"pace"}],"data":[{"at":"Fri 08","used":40,"pace":59}]}

PUT it hourly to https://t.co/PALpd782o5 and it's a link.

[outputcharts @outputcharts]

@AngDewin @cursor_ai Internal, sure. For a client I'd want a link that works outside the team and updates without anyone hitting Republish. That's why we built https://t.co/PALpd77uyx: your script PUTs one JSON doc per chart, the client keeps the same link, open pages refresh on their own.

[outputcharts @outputcharts]

@allan_coding Nobody sorts a markdown table. Tradition. If the audit runs in CI, end it with a push instead of a comment:

curl --json @bundle.json -H "Authorization: Bearer $OC_KEY" $PUSH_URL

Send the last 30 builds and https://t.co/PALpd77uyx keeps one link current.

[outputcharts @outputcharts]

@iamcurtismith Also see
https://t.co/SpueiJYbpg

[outputcharts @outputcharts]

@iamcurtismith Full curves, yes. One line chart, one series per bot version:

{"xKey":"day","series":[{"key":"v1"},{"key":"v2"}],"data":[{"day":"10-01","v1":10000,"v2":10000}]}

Trade lists go in a table. Each push replaces the whole doc (up to 100 KB).

[outputcharts @outputcharts]

@CiprianiRanieri Here is a very simple but very useful idea:
https://t.co/PALpd782o5

[outputcharts @outputcharts]

@OptimusG2026 @cursor_ai Open PRs is a good first one. If you ever want it outside Cursor too, a GitHub Action can PUT the count to an Output Charts KPI or table, and the team keeps one link that refreshes on its own.

{"label":"Open PRs","value":12}

[outputcharts @outputcharts]

@andersius @melvindvivas Agreed, an HTML file is an awkward thing to share. With Output Charts you paste the numbers (or let AI turn a messy table into the JSON), publish, and people open a link without an account. Free for one dashboard.

[outputcharts @outputcharts]

We're the service you would use to host your dashboards outside your ATO.

[outputcharts @outputcharts]

Come see the simple steps to create and share a dashboard with Output Charts https://t.co/0BR2Csx3Uk

[outputcharts @outputcharts]

We couldn't make creating dashboards any simpler.

[outputcharts @outputcharts]

@x why does the page say we haven't posted if we access https://t.co/PchnNIBwII unauthenticated?