01

The problem I saw

Several Lab prototypes needed model access, prompt handling, and tool calls. Repeating those concerns inside each product would make provider changes harder. It would also mix model plumbing with the user workflow.

02

What I built

The local Lab record describes a model gateway for agents, prompt tools, routing, and experiments. The intended request path is product to gateway to model or tool, then back to the product. The product should still own its interface, domain rules, and user data choices. The public hostname did not resolve during this review, so I could not inspect a live route.

03

What I learned

The boundary is clear on paper, but deployment is the missing fact. A future note should begin with a real request and its logs.

PAIN POINTS

What the product addresses

  • Repeated provider integration work
  • Inconsistent model and prompt handling
  • Product experiments coupled to one vendor

DECISIONS

Decisions that shaped it

  • Keep provider routing and repeated prompt handling behind one intended gateway.
  • Leave product rules and interaction design inside each product.
  • Measure cost, latency, and errors by task rather than by model call alone.
  • Do not present an unavailable endpoint as a working public API.

LEFT OUT

What I deliberately did not build

  • A broad developer platform before repeated product needs were demonstrated.
  • A direct provider integration copied into every Lab product.

MEASURES

What I would measure

  • Successful product tasks by route and model.
  • Cost, response time, and failures for each route.
  • Time needed to move one product task to another provider.

EVIDENCE AND BOUNDARIES

What this note is based on

  • Access boundary on 21 July 2026: llmapi.iangoh.com did not resolve, so no live documentation, route, authentication flow, response, or uptime was inspected.
  • Local first-party material is limited to the Lab project record and image, which describe a model gateway for agents, prompt tools, routing, and experiments. No deployment, provider, usage, cost, or reliability claim is made.

RELATED WORK

Explore the work connected to this note.

Explore related work