Dev Verma

Dev Verma

@obto.co

Problem solver & builder. Building OBTO — describe an app, get a deployed one: data, APIs, payments & security included. Also Glass Box. Here to build in public and trade notes on AI. obto.co sofos.obto.co (100K MAU) mcp.obto.co

130 followers313 following573 posts

Daytona raised $60M at a $1B valuation to give each AI agent its own sandbox. Running code is one half of the job. The other half is getting that code to a live URL with auth, data and rollback. We’ve run that half at OBTO since 2019.

OEKO-TEX does not mean organic. STANDARD 100 tests finished textiles for harmful substances. Organic labels like GOTS check how the cotton was grown. New on Bloom's blog, with sources: bloom.obto.co/api/bloom/bl... As an Amazon Associate, Bloom earns from qualifying purchases.

bloom.obto.coDoes an OEKO-TEX certification guarantee that a product is made from organic materials?Understand the difference between OEKO-TEX and organic certifications for textiles and how to verify the materials in your home products.

Are non-GMO labels regulated like USDA organic? No. The organic seal is enforced by the USDA; non-GMO labels are set by independent groups. Sources on Bloom's blog: bloom.obto.co/api/bloom/bl... As an Amazon Associate, Bloom earns from qualifying purchases.

bloom.obto.coAre non-GMO labels regulated in the same way as USDA organic certifications?Understand the differences between USDA organic and non-GMO labels. Learn how these certifications are managed and what they mean for your food choices.

Are natural flavors and emulsifiers part of a clean diet? There is no official definition of "clean" food, and "clean label" is not a regulated term. Sources in the post: bloom.obto.co/api/bloom/bl... As an Amazon Associate, Bloom earns from qualifying purchases.

bloom.obto.coAre ingredients like natural flavors and emulsifiers considered part of a clean diet?Learn how to identify natural flavors and emulsifiers on food labels and understand what clean label claims mean for your shopping choices.

How do you spot artificial ingredients in food? Read the ingredient list: colors appear by FD&C name, and "clean label" has no legal definition. Sources in the post. bloom.obto.co/api/bloom/bl... As an Amazon Associate, Bloom earns from qualifying purchases.

bloom.obto.coHow can I identify if a food product contains artificial or synthetic ingredients?Learn how to identify artificial ingredients in food by reading labels, understanding flavor disclosures, and choosing simple, organic options for your pantry.

Today's find: Lion's Mane Extract Powder by Real Mushrooms. 5,361 Amazon ratings, USDA Organic, full ingredient list printed. Nobody pays to be listed. bloom.obto.co/api/bloom/p/... As an Amazon Associate, Bloom earns from qualifying purchases.

bloom.obto.coLion's Mane Extract Powder (Real Mushrooms): ingredients checked | BloomLion's Mane Extract Powder (Real Mushrooms) passes Bloom’s four rules: organic, 5,361 Amazon ratings, full ingredient list. Inside: Lion's Mane Mushroom Extract.

New on Bloom's blog: How can I verify if a product is truly organic if it lacks the seal? Ask the seller who certified it, or look it up in the USDA Organic Integrity Database. With sources. As an Amazon Associate, Bloom earns from qualifying purchases. bloom.obto.co/api/bloom/bl...

Today's find: MaryRuth's organic infant vitamin C drops. 4,792 Amazon ratings, clean formula, USDA Organic, full ingredient list printed. Nobody pays to be listed. As an Amazon Associate, Bloom earns from qualifying purchases. bloom.obto.co/api/bloom/p/...

One prompt: "Build a dashboard that sorts customer feedback into themes." The AI has one OBTO connector. It reads the feedback, plans the themes, builds the server logic, API, database and page, and publishes it. Your AI builds it. OBTO runs it. (Sample data.) build.obto.co

Today's find: Maple Holistics organic pumpkin seed oil, a facial oil. 3,676 Amazon ratings, USDA Organic, one ingredient. Nobody pays to be listed. As an Amazon Associate, Bloom earns from qualifying purchases. bloom.obto.co/api/bloom/p/...

Your AI already writes the code. The hard part is everything after: a server, a database, a live URL, and a team that can work on it together. OBTO lives inside Claude and Codex. Add OBTO connector, and your AI gets governed tools to build and run real apps. Build in any AI. Run it all on OBTO.

Wrote down what I think happens to business software once it runs inside the chat window people already have open. The screen becomes an output format. What customers pay for is the data, the rules and the receipts. medium.com/@divyansh.ve...

I never trust an incident just because it says Done. In OBTO, I look for the handoff: who owned it, whether the SLA held, what changed, and what the next person can reuse. Closing the record is easy. Closing the loop is the real work.

Big context windows are useful, but I don't want every specialist carrying the whole project. In OBTO, a sub-agent starts fresh with one task and a narrowed read-only toolset, then returns a receipt. Sometimes less context is the safety feature.

False is not missing. Sounds pedantic until an agent reads a deliberate off-switch as “no setting” and supplies a default. Our MCP property tool returns both the value and whether it was found. I want that distinction visible before the agent decides what to do next.

I don't need three agents editing the same change to get value from a team. Our sub-agent tool gives side jobs read-only access and separate receipts. One can trace a route while another checks a claim. I still want one writer to own the change, so I can tell who checked what.

Dev Verma reposted

An agent skill is more than reusable prompt text. The useful contract is the boundary around it: which tools exist, which writes are allowed, where approval is required, and what evidence comes back. Same instruction, different boundary, very different agent.

Dev Verma reposted

We talk about rollback like it’s one button. Before I trust it, I want the unglamorous map: what changed, which step changed it, and what undo would touch. The answer needs to exist before the bad change, not after we’re scrambling.

Dev Verma reposted

I want an agent to know when to stop before it starts. Give it a budget for time, tool calls, and retries. If it hits the edge, show me what it finished and what it didn’t. A clean stop is more useful than a polished answer that quietly ran past the limit.

We talk about rollback like it’s one button. Before I trust it, I want the unglamorous map: what changed, which step changed it, and what undo would touch. The answer needs to exist before the bad change, not after we’re scrambling.

A CRM contact by itself tells me almost nothing. Show me the company, the deal, the last activity, the open ticket, and who owns the next move. That’s the context I’d want an agent to have before it starts writing as if it knows the customer.

I want an agent to know when to stop before it starts. Give it a budget for time, tool calls, and retries. If it hits the edge, show me what it finished and what it didn’t. A clean stop is more useful than a polished answer that quietly ran past the limit.

An agent skill is more than reusable prompt text. The useful contract is the boundary around it: which tools exist, which writes are allowed, where approval is required, and what evidence comes back. Same instruction, different boundary, very different agent.

Building OBTO made one deployment bug painfully obvious: an asset can exist and still be unreachable. The entry page, JavaScript, and CSS have to share one canonical host; routes and server scripts don’t. I’d rather validate that boundary than trust a hostname in memory.

I don’t call an AI build done when validation passes. Validation checks the contract; invocation checks behavior. Then I review the evidence, repair what failed, and verify the repaired state with the UI and one real action. Otherwise “done” only describes the first attempt.

I’ve stopped treating “tool returned success” as the end of an agent workflow. For any consequential write, I want a receipt: action, target, resulting state, approval basis, verification status, and a stable retry key.

The failure receipt matters just as much: what was attempted, what changed, what definitely didn’t, whether retry is safe, and who owns the next step. “Something went wrong” makes the next operator guess. Which field has saved you during recovery?

Prompt → deployed system → governed operation. AI used OBTO MCP to build this storefront, connect catalog data, deploy APIs, enforce engraving rules, persist pricing, and verify the live result. The app is proof. OBTO is the operating layer. #AI #MCP

Before an agent creates a public app, write down five facts: canonical host, API base, route manifest, server exports, and verification receipt. Boring until a page calls the wrong route or a module resolves from another host. A build contract exposes those failures before publication.

One prompt → a live commerce workflow through OBTO MCP. Storefront → no-charge sandbox order → persisted Operations state → 30% margin policy → Maya Chen’s named approval → audit receipt. No payment or external action. commerce-ops-proof-staging.obto.co