About
What this site is, and what it refuses to be
bitpull.io documents a product it does not sell. That constraint is the reason it can be useful - and it only works if the statuses on every page are true.
Four domains, four jobs
bitpull.io is one of four domains operated by NEOB Technology GmbH in Vienna, Austria. They are deliberately not interchangeable, and none of them is a mirror of another.
| Domain | Job | Answers |
|---|---|---|
neob.dev | Research & development | What might be possible. Agentic, realtime and multimodal AI, at NEOB Labs. |
neob.ai | Company | Who builds this. Enterprise AI, consulting, custom work. |
bitpull.io | Developer platform | How to build and integrate. This site. |
bitpull.ai | Product | Why to use it, and where you actually create and run an agent. |
The short version: bitpull.io explains how to build and integrate; bitpull.ai is where you buy and run it. Everything on this domain is written on that assumption, which is why there is no pricing page here and no industry landing pages.
How a status is decided
Every capability documented here carries one of seven statuses. They are not marketing gradations - each has a test:
| Status | The test it has to pass |
|---|---|
| Available | A dashboard control or a documented endpoint does it, today, without anyone's help. |
| Beta · account flag | It is built, but hidden behind an account capability flag. You may not see it in your dashboard at all. |
| Assisted setup | It runs in production, and the connection is set up together with the bitpull team rather than by you. |
| Via webhook | No connector exists. The post-conversation webhook carries the data, and code you own does the rest. |
| Via API | No connector exists. The public REST API or a declared tool gets you there. |
| Planned | Named as a direction, not callable. Do not plan a launch around it. |
| Research | Explored at neob.dev. No product commitment of any kind. |
The rules this site holds itself to
- No invented endpoints. The API reference was written by reading the platform's own client and its published documentation. If something is not on the API page, this site treats it as not public.
- No invented payloads. The webhook envelope is not a published contract, so no page here prints a field list as if it were one. Pages send you to capture a real delivery instead - which is also why the tester exists.
- Absence gets a page. No SDK, no MCP, no Outlook connector, no playground. Each of those has a page saying so, because a developer's most expensive discovery is the one made in week three.
- Third-party code is attributed. Snippets against HubSpot, Shopify, Slack and Microsoft Graph use those vendors' public APIs and say so.
- Where the vendor and reality disagree, both are shown. The
data-modesvalue on the embed page is the current example.
A page here can go stale the moment the platform ships something. If a status is out of date or a snippet no longer works, support@bitpull.ai reaches us - corrections are more useful to this domain than new pages.
What is deliberately absent
- Pricing. It belongs on bitpull.ai, where it can be kept correct.
- An ROI calculator. bitpull.ai already has one. A second, slightly different calculator on a second domain competes with the first for the same search and gives two answers to one question.
- Industry landing pages. Hotels, clinics, workshops - those are commercial pages and they exist on the product site.
- An account. Nothing here needs a sign-in, and nothing here stores anything about you beyond what a tool needs while you have it open.
Privacy, in one paragraph
No analytics scripts, no third-party fonts, no external requests from the pages you read. The two interactive tools that need a server are the webhook tester, which holds captured requests in memory for thirty minutes, and the status page, which asks the bitpull API whether it is up. The widget generator, prompt reviewer and latency test never send anything anywhere. The full statement says the same thing at length.