Kelvin Biffi
EN PT
Résumé

AI Engineer · Design Engineer

I design the part of AI people have to trust.

Chat is the easy part. I build the approval card, the refusal, the citation, the cost meter, and the validation layer underneath that keeps the model honest.

15+
years shipping
5
MCP servers built
3,700+
users on my SaaS
1M+
behind a login I led

What I do

Two halves of the same job.

Agents and MCP

Agents with tool calling, MCP servers with real auth, retrieval that knows each user. Explicit orchestration, so every tool call stays inspectable.

Interfaces people trust

The screens after the chat: approvals for irreversible actions, refusal states, citations, cost, diffs to review. Fifteen years of frontend in production behind them.

The layer underneath

Model output validated like user input: schema, field assertions, guardrails that can refuse, and failure that is explicit instead of silent.

Selected work

Products I designed, built and run.

All work

Model Context Protocol

Five MCP servers. Your assistant can already use them.

I wrote the book on MCP in Portuguese, then shipped these to production, which is a very different experience.

44 tools

How I build

An agent does not fail loudly.

It returns something plausible, the logs look clean, and weeks later someone finds a corrupted record. So these are the rules.

  1. 01

    Validate output like user input

    A successful API call says nothing about whether the payload makes sense.

  2. 02

    Refusal is a feature

    When the answer is not in the source, "no" is the correct output. Design that screen.

  3. 03

    Deterministic first

    Checks that cost nothing run before any model judges anything.

  4. 04

    Cost per conversation

    Not per call. A conversation is what a business can price against.

  5. 05

    Humans approve the irreversible

    No agent writes to a CRM, sends outreach or spends budget without passing a gate.

  6. 06

    Traceability is not verification

    Citing a source is not the same as matching it. Numbers get checked against the source.

Off hours

I also make games.

Five published on itch.io, scored with an AI music studio I built for that reason.

Pick a game

Ask the machine

An agent that cannot make things up.

ASK-1 answers about my work by quoting its sources, never by generating text. Every answer shows where it came from, and when the answer is not there, it says so. No model call, no API key on the server, nothing to abuse.

ASK-1 retrieve → rank → quote → cite

Ask anything about my projects, stack or experience. Pick a suggestion to start.

Model calls 0 Cost $0.00 0 questions

Beyond the code