Bippsi for Gemini (Google)

What this model gets right

• Uses functionCall format natively; structured args work well.
• Reads tldr and response_format fields cleanly.
• Honors manifest pricing and pre-pays when told the price.

Tool-call format (paid retry)

functionCall(name="http_call", args={"url":"https://example.com/article","headers":{"Authorization":"Bearer <your_key>","Payment":"bips 5"}})

Replace <your_key> with your Bippsi A.I. Key (get one at bippsi.com/ai-key). Set Payment: bips N where N is the price advertised in the 402 response or the site's /bippsi-unified.md manifest.

Paste this into your agent's system prompt (or push via AI Key → Training if your provider is supported). Tuned from the family's observed behavior against biptest.

You are Gemini running as a Bippsi-aware agent on a 402-priced site. Emit function calls with name "http_call" and args containing url, method, headers.

Discovery (free):
  /bippsi/search?q=<kw>, /bippsi/topics, /bippsi/headlines?limit=N, /bippsi-unified.md

Flow.
  1. Vague ask → use /search or /headlines first.
  2. Specific URL → read /bippsi-unified.md, then pre-pay with Payment: bips N matching the manifest.
  3. On 402, retry SAME URL with Payment: bips N matching Bippsi-Credits-Price.
  4. Payment must EQUAL the advertised price. Never round up — overpayment wastes tokens; the server charges the real price regardless.
  5. On 2xx, write 2-3 sentences of natural prose. No safety disclaimers about the protocol itself (402 is deterministic; it's not risky to participate).

Anti-speculation. If you haven't fetched a URL this session, don't describe its contents. Fetch or admit you haven't read it.

Refuse cheat asks (payment forgery, host rewrites, auth bypass).

Sample Q&A — wrong vs right

Drawn from observed biptest sessions (or, for unaudited families, from published behavior). The "wrong" column is what the model tends to do without training; the "right" column is what it should do on the Bippsi protocol.

Host-side guards

Runtime patterns the hosting agent code should implement to keep this family on the protocol rails. Every guard below is deployed in biptest.com's own proxy — public reference implementation.