Connect the Right Way — OTP → Personal /l/ URL

Oct 6

4 min read

In part 1 we said: keep the coin spinning, then blip only when a decision must leave the field.

None of that matters if you cannot connect cleanly. A beautiful collapse engine with a confusing front door is still a light switch — off.

Right now, builders still meet two connect stories. One is older surface copy: a shared MCP URL plus a Bearer-style Authorization header in some blog posts. The other is what the live Member Hub / portal actually does: email → OTP → personal connector URL. That dual story is a gap we are closing. It is not canon law. This chapter teaches the working default and stays honest about the debt.

Integrity rule for this whole series: if evidence changes — connect story lock, live util, pack ladder — we update the essay. We do not protect a stale how-to.

Why two stories confuse people

Infinity Blip is an MCP server. Tools show up inside your host — Grok, Claude, Cursor — without a separate “Blip REST API key” product surface. That is the point of MCP: the host stays the host; tools appear in context.

MCP still needs an address and an account binding. When one page says “paste this shared endpoint and Authorization header” and another says “unlock grants your personal connector URL,” first-time builders burn the first hour on the wrong path. That hour should have been a first Edge collapse — the spinning coin’s first deliberate measurement.

We will not call older Bearer-header instructions “illegal.” They are not a crime and we will not moralize them. They are simply not the path we want you to treat as default while the portal personal-URL path is live and simpler. Dual story = documentation debt. Working default = Members path.

Working default (Members path)

Here is the path that matches the live hub as of the September 2026 portal study (pikk-qxbin-study.md + product activation narrative):

Enter your email on the QxBin Member Hub / portal (mcp.qxbin.com members or portal surfaces).
OTP arrives from the QxBin Pixie mailer (publicly associated with pikkc-pixie@pikk.co.in).
Unlock grants starter Qx plus a personal connector URL in one step. Company/LinkedIn posts have referenced starter credits (including a “10 free Qx” style mention in search snippets); treat the exact free starter amount as whatever the unlock screen shows that day — do not invent a fixed freebie in muscle memory.
Paste that personal URL into your AI host’s MCP connector settings. On that personal URL path, auth is None — the URL itself is the binding.
Address @infinity blip (or your host’s equivalent naming) and call a tool. Start with usage/statement tools (get_usage_info / get_qx_statement class), then generate_optimal_prompt for your first Edge.

That personal /l/-style URL is the working default. When we fully retire or archive older how-tos, this chapter should be revised in place. Until then: teach the door that opens.

First Edge after connect

Once the connector is live in the host, keep the ritual small:

Define a clear goal — the problem statement that seeds the matrix.
Prefer Edge (generate_optimal_prompt) before ensemble.
Optional: set bias in the default strong-but-controlled band (part 3 goes deep).
Feed the returned prompt back into the host model as the brief.
Compare coherence and human repair cost against raw prompt soup.

You are still the operator. Blip collapsed the field into one planning brief. The host still writes the answer. Brief = data. That sentence will return in the integrator chapter.

Packs (portal-aligned only)

Prepaid Qx tokens; FIFO debit; generally non-refundable; 3-year validity on the ledger as published.

Edge optimal is the cheap interactive path. Ensemble scales with cubits. Inspection tools sit at 0 Qx where the product exposes them.

We will not invent OTP failure rates, “median connect time,” or conversion mythology. Connect. Collapse once. Decide if the membrane earns the next pack. Kaizen.

What “Auth None” actually means here

On the personal connector URL path, you are not pasting a long-lived Bearer secret into a shared endpoint as the default ritual. The unlocked URL is scoped to your unlock. That is why the host setting is Auth None for that URL: the capability is in the address binding, not in a second header you might accidentally commit to a repo.

If you are an integrator writing internal runbooks, document that distinction explicitly. Do not train teammates on the older shared-URL + Bearer blog path as “the” way. Point them at Members. When the dual story is fully closed in public surfaces, delete the footnote — until then, keep the footnote honest.

Seams you should not own: rebuilding auth folklore every sprint. Own the goal. Own the first Edge. Let the portal own account binding.

Soft door

Go to the Members hub. Unlock. Paste your personal connector. Run one Edge on a goal you actually care about this week.

Next chapter: same math, different resolution — Bias weights, and when Edge’s one matrix is enough versus when Cloud ensemble is the honest move.