HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
AgentOps-AI
Jaiqu
Python2024–2024
AgentOps-AI / Jaiqu

Jaiqu

Automatically reformat any JSON into any schema with AI

2Distinct people
2Mentions
0Explicit recommenders
345GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Automatically reformat any JSON into any schema with AI

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 8:59:02 AM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by 6-hour interval2 dated mentions

Observed mentions: 2024-03-31 05:42:17 UTC to 2024-04-04 05:48:52 UTC.

012024-03-31 00:00:00 UTC to 2024-03-31 06:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsMar 31, 00:002024-03-31 06:00:00 UTC to 2024-03-31 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-03-31 12:00:00 UTC to 2024-03-31 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-03-31 18:00:00 UTC to 2024-04-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-04-01 00:00:00 UTC to 2024-04-01 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-04-01 06:00:00 UTC to 2024-04-01 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-04-01 12:00:00 UTC to 2024-04-01 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-04-01 18:00:00 UTC to 2024-04-02 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-04-02 00:00:00 UTC to 2024-04-02 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsApr 2, 00:002024-04-02 06:00:00 UTC to 2024-04-02 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-04-02 12:00:00 UTC to 2024-04-02 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-04-02 18:00:00 UTC to 2024-04-03 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-04-03 00:00:00 UTC to 2024-04-03 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-04-03 06:00:00 UTC to 2024-04-03 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-04-03 12:00:00 UTC to 2024-04-03 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-04-03 18:00:00 UTC to 2024-04-04 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-04-04 00:00:00 UTC to 2024-04-04 06:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsApr 4, 00:00

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Mar 31, 00:002024-03-31 00:00:00 UTC2024-03-31 06:00:00 UTC110
Mar 31, 06:002024-03-31 06:00:00 UTC2024-03-31 12:00:00 UTC000
Mar 31, 12:002024-03-31 12:00:00 UTC2024-03-31 18:00:00 UTC000
Mar 31, 18:002024-03-31 18:00:00 UTC2024-04-01 00:00:00 UTC000
Apr 1, 00:002024-04-01 00:00:00 UTC2024-04-01 06:00:00 UTC000
Apr 1, 06:002024-04-01 06:00:00 UTC2024-04-01 12:00:00 UTC000
Apr 1, 12:002024-04-01 12:00:00 UTC2024-04-01 18:00:00 UTC000
Apr 1, 18:002024-04-01 18:00:00 UTC2024-04-02 00:00:00 UTC000
Apr 2, 00:002024-04-02 00:00:00 UTC2024-04-02 06:00:00 UTC000
Apr 2, 06:002024-04-02 06:00:00 UTC2024-04-02 12:00:00 UTC000
Apr 2, 12:002024-04-02 12:00:00 UTC2024-04-02 18:00:00 UTC000
Apr 2, 18:002024-04-02 18:00:00 UTC2024-04-03 00:00:00 UTC000
Apr 3, 00:002024-04-03 00:00:00 UTC2024-04-03 06:00:00 UTC000
Apr 3, 06:002024-04-03 06:00:00 UTC2024-04-03 12:00:00 UTC000
Apr 3, 12:002024-04-03 12:00:00 UTC2024-04-03 18:00:00 UTC000
Apr 3, 18:002024-04-03 18:00:00 UTC2024-04-04 00:00:00 UTC000
Apr 4, 00:002024-04-04 00:00:00 UTC2024-04-04 06:00:00 UTC101

What Hacker News says

1 sources
Areibman·Mar 31, 2024Submission

Show HN: Write JSON processor queries (jq) in natural language

Hey HN! Jaiqu is an AI agent for creating repeatable JSON transforms using jq query language syntax. Jaiqu translates complex JSON structures into repeatable jq queries. jq is a command line utility built for fast, reliable JSON queries. Jaiqu takes advantage of the LLMs for both constructing jq queries as well as using feedback to fix errors/invalid results if those queries are incorrect. Writing code to parse JSON is super annoying. It usually involves manually reading huge JSON balls, parsing the keys in a language of your choice, and pulling the data manually. Also, you're likely to run into key mismatches (i.e. source data might have "customer_id" as a key but my table is "user_id"), so you would have to write the translation dictionaries by hand. This struck me as a task that was analogous to the many AI "natural language to SQL" ed
Read the rest
itors out there. However, there were a lot of consistency issues where the LLMs would not produce functioning code. So I wrote an AI agent that does it for me. It only takes two args: 1. A blob of messy JSON containing data you want 2. A JSON schema formatted in the way you want Jaiqu generates a repeatable jq query that collects the data in the exact JSON schema you specify. This way, you can run this query as many times you want or save it as a config without having to prompt LLMs each and every time. This tool beats the standard "prompt ChatGPT for a jq query" because by and large, LLMs don't perform too well when writing DSLs like jq. Jaiqu essentially works by: 1. Fuzzy matching each key against your schema to make sure it's available to query 2. Writing individual jq queries to fetch and transform those keys 3. Compiling each individual query into a single complex jq query. 4. Feeding back any errors or data mismatches to a "self-healing" loop that adjusts the queries accordingly until it works. Would love to hear thoughts or feedback. This has saved our team a ton of time internally, so hopefully it can help others as well.
38 points · Open discussion

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.