The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Back to feedPost
Webhooks are great until you are staring at logs, guessing whether a request actually arrived, or trying to inspect a payload that vanished into the void.
So I built Hookwise.
Hookwise gives you a private webhook endpoint in seconds, captures incoming requests, and lets you inspect payloads while you build and debug.
No card. No setup ceremony. Just create an endpoint and start catching requests.
It is free to use for now, and I would love to hear what you would use it for or what would make it more useful.
Try it here:
https://tryhookwise.vercel.app/
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Related posts
Agent Evaluation Dashboard — Full-Stack LLM Observability Tool
Teams running AI agents in production need visibility into how those agents actually perform not just whether they respond, but how accurate, fast, and cost-efficient they are. I built a full-stack observability dashboard to solve exactly that: a single place to track accuracy, latency, API cost, and schema compliance across multiple LLM models and agent types.
What I built
A responsive Next.js (App Router) frontend styled with Tailwind CSS — deep purple sidebar, live accuracy/latency charts (Recharts), filterable eval-run tables, and per-model performance comparisons
A Python FastAPI backend serving the dashboard's data layer, with token-based authentication protecting every route
Full session handling: login, protected pages, automatic redirect for unauthenticated users
A fully responsive layout collapsible drawer sidebar on mobile, reflowing grid on tablet/desktop
We build remote MCP servers — the piece that lets Claude and ChatGPT actually call your API instead of guessing about it.
Two we run in production right now:
• korea-data-mcp — 6 tools over Korean public-data APIs
• korea-ocean-mcp — 8 tools over Korea's marine and weather observation data (tides, sea temperature, buoy readings)
Both are remote (hosted, not a local stdio script), so a client pastes one URL into Claude Desktop, Claude Code or any MCP-capable client and the tools show up.
Three things we learned building them:
1. The hard part isn't the protocol, it's tool design. Six well-named tools beat thirty thin wrappers, because the model has to choose correctly without reading your docs.
2. Auth belongs on the server. Never make a user paste an API key into a chat window.
3. Error messages are prompts. "No station found for that name — try one of: ..." lets the model recover; "400 Bad Request" does not.
If you have a public or internal API and want it usable from Claude/ChatGPT, that is what we do. Typical delivery: 5 days.
ByaheroApp — Local Delivery Web App
I developed the customer ordering flow for ByaheroApp, a delivery platform designed for local merchants. Customers can browse merchants and products, add items to a cart, enter delivery details, and place cash-on-delivery orders. I also built a merchant dashboard for viewing incoming orders and worked on the Supabase database that stores merchants, products, orders, and order items.
The project uses Next.js and Supabase. My work covered the app’s frontend, order flow, database integration, and troubleshooting across the customer and merchant views. Admin management is still in development.
