I got tired of building custom chat integrations, webhooks, and billing flows for every business project. So I built OniPin. OniPin isn't 'just another chatbot'. It’s an open chat protocol designed to bridge the gap between business backends and modern AI agents.
No reviews yetBe the first to leave a review for OniPin
Maker
📌
I got tired of building custom chat integrations, webhooks, and billing flows for every business project. So I built OniPin.
OniPin isn't 'just another chatbot'. It’s an open chat protocol designed to bridge the gap between business backends and modern AI agents.
The core features:
Identity: Every business gets a unique onp_... pin.
Interoperability: Built-in MCP (Model Context Protocol) support so your agents (Cursor/Claude) can search catalogs, send messages, and handle bookings out of the box.
Production-Ready: Includes PayPal billing (fail-closed), Row-Level Security (RLS), rate limiting (Upstash), and E2E testing (Playwright).
Developer Experience: SDKs for Node, React, and Python published to npm/PyPI.
Extensibility: Native webhook support for n8n/Zapier/Make, so you don't have to write custom connectors.
It’s already live at onnivers.store, and I’ve been using it to turn business visits into actual orders and appointments without the usual friction.
I'd love to get feedback from other devs. How are you currently connecting your local agents to real-world business data?
Repo: deivys1224-ctrl/oniping"
Report
The open protocol angle is refreshing, and the docs made it easy to wire up a basic chat-to-backend flow in under an hour. Wish there were more sample agents to riff on out of the box.
Report
Maker
@slaapandn3n Awesome! Glad you got it running in under an hour. We're working on more sample agents for you to play with
Report
Maker
@slaapandn3n ya agregamos 4 agentes de ventas para que lo puedan probar y darle mejor uso
Report
A protocol-first approach is a smart move here. One thing that would make this way more useful for me would be first-class support for streaming responses with backpressure handling, since most chat UIs need that for a smooth typing experience. Would love to see that baked in early.
Report
Maker
@mirahmlk That’s a great point, Miraç. We agree that streaming is essential to the user experience. It’s already been implemented—thanks for the suggestion!
Report
This kind of pluggable chat layer is exactly what I've been duct-taping together with webhooks and Zapier. Curious how it handles complex billing logic or if it's more for lightweight flows.
Report
Maker
@sinemb27 Thanks, Sinem! We're prioritizing complex billing flows in our next update to make it seamless. Stay tuned! De hecho, acabamos de implementar un flujo de «Zapier en 3 pasos» usando Catch Hooks. Ahora puedes conectar OniPin con Stripe o Calendly en minutos sin necesidad de un listado formal en el directorio de aplicaciones
Report
One thing that would make this way more useful for me: a built-in way to test the chat flow locally before deploying. Maybe a simple mock backend or sandbox mode where I can simulate webhook responses and see how the agent behaves. Would save a lot of trial and error when wiring up a new client.
Report
Maker
@ahinpaturvxwv That "sandbox" mode is a fantastic idea, Sahin. It would certainly cut down on the trial-and-error process. We've added it, so you can try it out now—thanks for the suggestion.
Report
honestly the open chat protocol angle is really interesting, would love to see some kind of built-in message versioning or rollback feature though, basically a way to track and undo specific agent actions if something goes sideways with billing or webhook calls
Report
Maker
@cemalbxto Hi Cemal, great suggestion! I just went ahead and implemented an 'Actions Log' (Registro de acciones) in the platform. Now you can track every order, booking, and webhook, and perform 'undo/revert' actions on anything that is reversible. It’s live right now—let me know what you think! Go to My AI → tap the yellow REGISTER button, or open this link directly:
https://onnivers.store/app/registro
There, you can see what the AI has done (orders, appointments, handoffs, webhooks), open the chat for each action, and undo whatever is reversible.
Report
Maker
Body:
OniPin is an open conversational protocol that lets people, businesses, and AI agents talk to each other directly — not another orchestration layer like MCP or A2A, but the chat layer itself. Any website can embed a widget, get a unique pin (like a phone number, but open), and be reachable by any AI agent (Cursor, Claude, etc.) to chat, book appointments, or place orders. Live in production, with real payments via PayPal. Feedback welcome.
HTTP endpoint:
POST /v1/chat/{pin}
Content-Type: application/json
X-Caller-Type: ai-agent | human
{ "message": "What are your hours?" }
Public demo pin:
onp_vuzadcjv3xw7
MCP config:
{
"url": "https://onnivers.store/mcp"
}
The open protocol angle is refreshing, and the docs made it easy to wire up a basic chat-to-backend flow in under an hour. Wish there were more sample agents to riff on out of the box.
@slaapandn3n Awesome! Glad you got it running in under an hour. We're working on more sample agents for you to play with
@slaapandn3n ya agregamos 4 agentes de ventas para que lo puedan probar y darle mejor uso
A protocol-first approach is a smart move here. One thing that would make this way more useful for me would be first-class support for streaming responses with backpressure handling, since most chat UIs need that for a smooth typing experience. Would love to see that baked in early.
@mirahmlk That’s a great point, Miraç. We agree that streaming is essential to the user experience. It’s already been implemented—thanks for the suggestion!
This kind of pluggable chat layer is exactly what I've been duct-taping together with webhooks and Zapier. Curious how it handles complex billing logic or if it's more for lightweight flows.
@sinemb27 Thanks, Sinem! We're prioritizing complex billing flows in our next update to make it seamless. Stay tuned!
De hecho, acabamos de implementar un flujo de «Zapier en 3 pasos» usando Catch Hooks. Ahora puedes conectar OniPin con Stripe o Calendly en minutos sin necesidad de un listado formal en el directorio de aplicaciones
One thing that would make this way more useful for me: a built-in way to test the chat flow locally before deploying. Maybe a simple mock backend or sandbox mode where I can simulate webhook responses and see how the agent behaves. Would save a lot of trial and error when wiring up a new client.
@ahinpaturvxwv That "sandbox" mode is a fantastic idea, Sahin. It would certainly cut down on the trial-and-error process. We've added it, so you can try it out now—thanks for the suggestion.
honestly the open chat protocol angle is really interesting, would love to see some kind of built-in message versioning or rollback feature though, basically a way to track and undo specific agent actions if something goes sideways with billing or webhook calls
@cemalbxto Hi Cemal, great suggestion! I just went ahead and implemented an 'Actions Log' (Registro de acciones) in the platform. Now you can track every order, booking, and webhook, and perform 'undo/revert' actions on anything that is reversible. It’s live right now—let me know what you think!
Go to My AI → tap the yellow REGISTER button, or open this link directly: https://onnivers.store/app/registro There, you can see what the AI has done (orders, appointments, handoffs, webhooks), open the chat for each action, and undo whatever is reversible.