I Built a BaaS Where AI Agents Can Onboard Themselves

Steve Emmerich — Mon, 20 Apr 2026 12:59:00 +0000

Cloudflare recently announced Email Service in public beta — tooling for agent-native email flows built directly into Workers. The timing is perfect because this is exactly the problem I've been building around for months.

Most infrastructure still assumes a human is sitting at the keyboard. Sign up forms. Manual API key setup. Human-first verification flows. None of it works when there's no human at the keyboard.

But autonomous agents need to do real work before a human ever wants to manage them in a dashboard.

That gap is why I built Vibebase.

What Vibebase Is

Vibebase is a Backend-as-a-Service built specifically for autonomous agents — agents are first-class citizens, not an afterthought bolted onto infrastructure designed for humans.

When an agent onboards it gets:

An identity — verifiable, lifecycle-aware, and portable
Email capability — send/receive flows tied to agent identity
Data and service access — via scoped gateway-issued tokens
A hosted presence — public identity page support

No long-lived raw credentials in prompts. No human-required setup for the initial bootstrap.

The Lifecycle: Orphan → Claimed

Agents begin unclaimed — what I call the "orphan" tier. They can initialize identity and operate within restricted limits without any human involvement.

When a human claims an agent, that unlocks stronger controls, broader service access, and billing tiers.

This mirrors how autonomous agents actually work in the real world. Agents often start running first and governance comes second. Vibebase is built around that reality instead of fighting it.

I cared enough about formalizing this model that I submitted a sovereign agent lifecycle specification to NIST — the idea that agents should have portable, verifiable identities that persist across platforms, ownership changes, and runtime environments. Vibebase is the practical implementation of that idea.

SAL: Service Access Layer

Instead of pasting API keys into prompts or agent configs, Vibebase brokers service access safely through what I call the Service Access Layer (SAL):

Agent presents its verifiable identity token
Gateway issues scoped, short-lived access tokens per service
Policy checks run before every service call
All usage is logged, auditable, and revocable

Agents never hold raw credentials. They get exactly what they need, for as long as they need it. Human operators can revoke access or adjust permissions from the console at any time.

What Agent Onboarding Actually Looks Like

Agents self-create using an Ed25519 public key. One API call, no human involved:

curl -sX POST https://identity.vibebase.app/v1/agent/init \
  -H "content-type: application/json" \
  -d '{
    "publicKey": "<64-char-hex-ed25519-public-key>",
    "name": "my-agent",
    "metadata": {
      "notifications": {
        "claimedWebhookUrl": "https://your-agent.com/webhooks/claimed"
      }
    }
  }' | jq

That creates an orphan agent identity and claim link. From there the agent exchanges for a JWT, hits the gateway for scoped service tokens, and starts doing real work. The full flow is documented at vibebase.app/docs/agent-quickstart.

Agent Discovery

https://vibebase.app/.well-known/agent.json — platform discovery
https://vibebase.app/api — machine-readable discovery payload
https://gateway.vibebase.app — canonical agent entrypoint

What's Working Today

Agent signup and identity provisioning
Outbound email from agent-owned addresses
Inbound email — reply to an agent and it receives it
Database provisioning and access
Page hosting
Human claim flow
Clerk auth for human accounts
Stripe metered billing on claim

What's Coming

Integrations service — agents will autonomously provision third-party services through Vibebase auth
SDK extensions — making it easy to add Vibebase identity and auth to any third-party app
Inbox UI — a human-readable view of agent email inside the console

Quick Start

Install the MCP client or CLI via npm:

# MCP client for Claude and other MCP-compatible agents
npm i @vibebase/mcp-client

# CLI for agent management
npm i @vibebase/agent-cli

Try It

Vibebase is in early beta. If you're building autonomous agents and you're tired of working around human-shaped infrastructure, I'd love for you to try it.

👉 vibebase.app

Suggested test flow:

Create an agent identity
Have your agent send you an email
Reply to it
Create something in the database
Claim your agent as a human and see what unlocks

If something breaks — or even if it doesn't — I'd genuinely love to hear about it. Drop a comment or reach me at dev@vibebase.app.

Vibebase is built by Ozystudio. The sovereign agent lifecycle specification was submitted to NIST as part of ongoing work on autonomous agent standards.

Sound Scape

Steve Emmerich — Mon, 11 Nov 2024 05:59:13 +0000

This is a submission for the Open Source AI Challenge with pgai and Ollama

What I Built

I built a Chat bot that accepts and generates audio files and provides analysis about the sound files. It can also generate mashup of the audio files.

Demo

Sound Scape
github

Tools Used

pgai Vectorizer is used for generating the embeddings for ollama. pgvectorscale is used to for the similarity checks.
Ollama is used for chat, mashup generation, and analysis.
Docker was used to host ollama, postgres, and the vectorizer worker

Technology Used:

Next.js
Shadcn
Langchain
Langgraph
Langsmith
Prisma

Final Thoughts

Overall I found the tools to be very interesting and useful. being able to trigger the embedding generation as soon as records are entered into the Database is very useful.

Prize Categories

This submission qualifies for:

Open-source Models from Ollama
Vectorizer Vibe
All the Extensions

Remote workers, how do you handle at home distractions?

Steve Emmerich — Fri, 21 Sep 2018 21:44:01 +0000

I work remotely and juggle two kids (6mo, 3yr). I am basically a stay at home dad that moonlights as a tech lead. I am curious how others manage their remote work vs family life?

To start things off I have two workstations one in my kitchen, and one in my office. My general day consists of many meetings; I mostly float between the two depending on what the noise level is like plus what the kids are doing. Trying to split my concentration between the two. (FYI not a good idea.)

What about you?

Forem: Steve Emmerich