StitchApi | Devpost

Inspiration

Every day, all of us switch between too many apps just to understand what’s happening in our life.

Meetings in Google Calendar.
Important emails buried in Gmail.
Learning on YouTube.
Work in GitHub.
Music on Spotify.
News from 5 different sources.
Market updates from stocks and crypto apps.
Knowledge scattered across Wikipedia.

No clarity.
No single view.
Just endless tab-switching, distraction, and chaos.

We asked ourselves:

“Why can’t all these apps talk to each other?”
“What if one API could summarize your entire digital world?”

That became the core inspiration behind HexAPI - A Frankenstein-style stitched creation where ANY apps can merge into one intelligent endpoint.

And thanks to Kiro, we didn’t just imagine it.
We built it.

What it does

HexAPI lets you:

Connect ANY number of apps or APIs
Email, Calendar, YouTube, Spotify, GitHub, Stocks, Crypto, Wikipedia… anything.

Stitch them into ONE “super-endpoint”
Example endpoints created inside our app:

/morning-briefing
/creator-hub
/student-study-digest
/founder-dashboard

View everything from one dashboard
No more jumping across tabs.
No more fragmented information.
Just clarity.

Customize your merged data anytime
Choose which fields you want.
Add or remove apps.
Rebuild the endpoint instantly.

Chat with the merged data
Our built-in chatbot lets you ask:

“Summarize my day”
“What changed since yesterday?”
“Extract only urgent tasks”
“Explain today’s market movement”

Automatically generate SDKs
Your unified endpoint becomes a full JS SDK instantly.

One endpoint. One dashboard. One place to understand everything.

How we built it

Kiro was the core of our development , here’s how it powered us:

1. Vibe Coding

We described our idea to Kiro conversationally:

“We want a system that stitches any APIs into a single endpoint with a JSON spec interpreter.”

Kiro instantly generated:

project structure
endpoint engine
merging logic
schema interpreter

This saved us days of setup.

2. Spec-Driven Development

We wrote a simple spec defining how data should merge.

Kiro:

validated schemas
auto-generated types
ensured consistent outputs
rewrote transformation logic

It removed 90% of the complexity of merging incompatible APIs.

3. Agent Hooks

Hooks automatically:

pulled API metadata
refreshed schemas on changes
rebuilt endpoints
regenerated SDKs
validated field combinations

We focused on product features, Kiro handled the grunt work.

4. Steering Docs

We created small steering docs telling Kiro:

how to combine fields
how to format unified responses
how to generate consistent SDK code

Kiro followed these rules perfectly, improving precision.

5. MCP Integrations

We extended Kiro with MCP tools to:

load API schemas
fetch OAuth tokens
test endpoints
view raw API responses

This turned Kiro into our backend integration assistant.

Challenges we ran into

1. Every API speaks a different “language”

Different schemas, formats, errors, and auth systems.
Manually aligning them would have taken months.

2. Dynamic merging is extremely complex

We needed a system that could merge any 3–10 APIs without hardcoding anything.

3. Building a safe chatbot over merged data

We had to prevent hallucinations and create reliable explanations.

4. Making it simple for non-technical users

Stitching APIs should be magical, not confusing.

Thanks to Kiro’s specs, steering, and hooks , we overcame all of this.

Accomplishments that we're proud of

Built a fully working “Internet → One API” engine
Completely dynamic. No manual glue code.
Designed a dashboard where users see everything in one place
No more switching between apps.
Created a chatbot that understands merged data contextually
Users can talk to their connected apps.
Auto-generated SDKs for every super-endpoint
Developers can instantly integrate.
Built everything in under 48 hours because of Kiro
What normally takes 2–3 months was brought to life like a Frankenstein creation.