Omevision
The platform

What the five services actually do.

5 services · 11 products already on them

A spec sheet, then the drawings. You cannot screenshot an API, so the three you would integrate first are drawn instead — each figure draws itself once when it reaches you, then stops.

YeboID

Identity and single sign-on

One account across every system. Phone, one-time code and PIN, with OAuth and OIDC for anything that already speaks them.

YeboVerify

KYC, KYB and AML

Document capture, liveness and match scoring, with the record-keeping a regulator asks to see.

YeboPay

Payments and settlement

Cards, mobile money and invoicing behind one interface. A charge is paid or it is not; there is no third state.

YeboLink

SMS, WhatsApp and email

One send, routed to whichever channel reaches the person, reporting back which one landed.

YeboAI

Shared inference layer

The models, the tool index and the authorization gates every product calls, rather than a separate integration per product.

Fig. 01 / YeboID

Sign in once. Stay signed in everywhere.

The first visit costs your customer one login. Every product after that costs them nothing.

Swipe to see the whole drawing

Your customerFirst visit, any product1. /oauth/authorizeYeboIDOAuth 2.0 + OIDC, PKCEPasswords never leave hereISSUES SIGNED JWT2. Bearer access_tokenYeboShopsNo second loginYeboJobsNo second loginYeboMartNo second loginYour appNo second login
Every product verifies the signature itself against YeboID's key set. No shared session store, no password on the wire, no per-product account table.Operational
Fig. 02 / YeboVerify

The ten-second path to a known customer.

Five checks between a stranger and a verified account, running today inside a regulated financial institution.

Swipe to see the whole drawing

01CaptureID document, both sides02LivenessA real person, not a photo03Face matchAbove 90% match accuracy04ScreenSanctions and AML lists05ClearedAccount opensELAPSED0s2s4s6s8s10s< 10s
Under ten seconds is the verified figure. The per-stage divisions on the bar are drawn evenly because the stage-by-stage breakdown is not published — the total is the claim, not the split.Operational · regulator cleared
Fig. 03 / YeboPay

Your customer pays how they pay. You reconcile once.

Three rails in, one settlement out. You integrate the left side once and never touch it again.

Swipe to see the whole drawing

CardVisa, MastercardMobile moneyMoMo and local walletsYebo walletStored balanceYeboPayRouting, retries, invoicingOne ledger across all railsPAID / NOT PAIDYouOne settlementOne reconciliationHOWEVER THEY PAYSETTLED LOCALLY
A charge is paid or it is not. There is no third state, no silent partial, and no fallback that renders a failed rail as a successful one.Operational
The conversational layer11 products · one tool index

Yebo. One conversation. Everything done.

One assistant, signed in through YeboID, reaching every product over MCP. A shop owner restocks, pays the supplier and books the delivery in a single thread. No app to install. No staff to train.

See Yebo
Fig. 04 / Yebo Conversational OS

One sentence in. Real actions out.

The panel on the left is the shipped interface, animation and all. The trace on the right is what the orchestrator does with it.

Swipe to see the whole drawing

YeboLive

I need a welding job in Nairobi

Three openings near Nairobi. Two take applications right now.

Welder, structuralIndustrial Area, Nairobi · Full timeKES 62,000Apply
Fabrication assistantRuiru, Nairobi · ContractKES 41,000Apply
What happens underneath
  1. 01

    YeboID verifies the caller

    The token is checked against the key set. Everything below is scoped to that one subject.

  2. 02

    FastPath, then the router

    Greetings and confirmations never reach a model. Only the rest gets classified and routed to a tool.

  3. 03

    MCP call to the product

    yebojobs.listings_search → api.yebojobs.com/mcp

  4. 04

    The capability gate runs

    Searching is open. Applying needs a verified identity, so the gate decides before the button does anything.

  5. 05

    Results become cards, not prose

    Six card types ship today: listing, job, invoice, payment, verification, generic.

Connected surfaces11 / 11 MCP
  • Eneza
  • YeboLearn
  • YeboLand
  • YeboShops
  • YeboCars
  • YeboLift
  • YeboMart
  • YeboDash
  • Yebona
  • YeboJobs
  • YeboTickets

One tool index across every product. Adding the next one is a registry entry, not a rewrite — which is the entire reason the layer is worth having.

Bubbles, typing indicator and result cards are reproduced from the shipped app, at its own timings.11 / 11 products on MCP
Fig. 05 / YeboAgent

It also works when nobody is typing.

Chat is the reactive half. Agents are the other one: they wake on a schedule, a reminder or an event, act, and come find you.

Swipe to see the whole drawing

CRONEvery Monday, 07:00Real IANA zones, Africa/Lagosthrough Africa/CairoREMINDEROnce, at a set timeMust be in the future,or it is refusedEVENTWhen something happensA product fires,the agent answersThe tickRuns every minuteClaims only what is dueADMIN KEY REQUIREDThe runSame tools the chat usesSame gates, same limitsMCP FAN-OUT, CAPPEDIt finds youOut of band, whereveryou already are

Why the tick is locked

It starts paid runs and fans out to product servers. An open endpoint would be someone else’s bill and your outage.

Why it is capped

One tick fires a bounded number of triggers. A thousand due at once drains across ticks instead of taking the fleet down.

The part nobody else shows

Every competitor can demonstrate a chatbot answering. Almost none can show one that acted overnight and reported back.

A trigger belongs to exactly one person. Every read and every write is scoped to their subject, so a forged id matches zero rows and returns a not-found rather than someone else’s schedule.Operational
Next

Bring the objections. A technical review puts your engineers and ours on the architecture, the data boundary and the integration surface, before anything is scoped.

Book a technical review