Your first 60 seconds with IOOK

IOOK is designed around one idea: you should not have to keep your entire life in your head. You can give IOOK an obligation, a financial record, a travel request, or useful context about a person, and IOOK turns it into something structured that you can come back to later.

1. Choose your display currency under the IOOK logo, or leave it on Auto.
2. Use Inbox when you simply want to dump information into IOOK.
3. Use Accounts when the information is specifically about money.
4. Use Flights when you want to search or refine a trip.
5. Use Memory when you want to revisit people, places, and context IOOK has seen before.
6. Use PORUS for actions that require permission, payment, or execution.

Four pillars, one assistant.

Think of IOOK as the brain and PORUS as the hands. IOOK may understand that you want a flight; PORUS is the layer that will eventually be allowed to execute the purchase after the required confirmation and authentication.

The place to dump life admin.

Inbox is the broadest part of IOOK. It is for messages, bills, appointments, renewals, requests, notes, pasted emails, screenshots, documents, and anything else that contains something you may need to remember or act on.

What happens after you submit something?

IOOK sends the content to its interpretation layer. The system attempts to extract concrete actions, dates, times, categories, tags, people, places, and useful details. You review what it understood before saving the results.

A message can contain more than one action. IOOK is intended to split multi-step language into separate tasks instead of collapsing the whole message into one vague reminder.

Type it, paste it, upload it, or speak it.

Text

Type naturally. You do not need a special command format. Dates such as “Friday,” “tomorrow,” “20 November 2026,” or “Tuesday at 6 PM” can be interpreted using the current local date supplied by your browser.

Files

The Inbox accepts common files such as PDFs, text files, CSV files, and images. Accounts also has a dedicated financial-document upload path. File content may be sent through the IOOK server and the configured AI connection for analysis.

Voice

Press Speak, talk normally, and press Stop speaking when finished. The current beta uses browser speech recognition. The language selector can be changed between supported options such as English (India), Hindi (India), and English (US).

Today, Upcoming, and All tasks.

Once actions are saved, IOOK organizes them into task views. Today shows items due today. Upcoming shows future-dated items. All tasks is the complete task inventory.

Tags and categories

Tasks can carry broad categories such as Business, Finance, Travel, Family, Bills, Shopping, Subscription, Personal, Home, or Appointment, plus more specific tags. You can search across task titles, details, people, places, categories, and tags.

Completing vs deleting

A completed task can remain useful as history, especially because Memory profiles can use completed items to explain previous context. Deleting an item removes it from the browser’s task store, so use deletion more carefully than completion.

Give IOOK financial information and ask questions about it.

Accounts is IOOK’s financial-administration workspace. It is intended to understand money records rather than merely storing unstructured notes. You can paste transactions or upload statements, bills, invoices, receipts, and other financial documents.

What IOOK extracts

Depending on the source, IOOK can attempt to identify descriptions, dates, amounts, currencies, inflow/outflow direction, categories, document type, due dates, and payment status. The top summary shows totals such as Outflow, Inflow, Net, and Records.

Questions you can ask

Account currency filter

Account records keep their own native currencies. If the records include multiple currencies, the Accounts filter lets you focus on one currency without rewriting the underlying data.

What the Setu Account Aggregator section is for.

The connected-banking area is designed around India’s consent-based Account Aggregator model. The intended experience is: the user starts a consent request, the regulated AA/banking flow handles authentication, the user approves the requested data access, and IOOK can then fetch only the financial information covered by that consent.

1. Open Accounts.
2. Enter the mobile number associated with the supported financial account.
3. Press Connect bank.
4. Complete the external consent/authentication flow.
5. Return to IOOK and use Check consent.
6. When approved, the beta can create a data session and attempt to fetch the approved information.

What IOOK should never ask you for

IOOK should not ask you to type your internet-banking password, UPI PIN, card CVV, or bank OTP into the IOOK interface. Those credentials belong inside the regulated bank/payment authentication flow.

Auto-detection, symbols, and manual override.

The currency control lives directly below the IOOK logo. Auto first checks the browser timezone because that is often a better indicator of the user’s current region than the browser UI language. For example, Asia/Kolkata maps to ₹ INR.

Users can override Auto and choose INR, USD, EUR, GBP, JPY, SGD, CAD, AUD, CNY, or CHF. The preference is saved in that browser.

Flights and converted prices

Duffel may return the airline fare in a different currency. IOOK can display an approximate converted amount for convenience while retaining the original airline amount and currency underneath. PORUS must use the original offer data rather than silently changing the airline charge.

Search conversationally, refine naturally.

Flights is a dedicated travel conversation, separate from the general Inbox. The current integration can use Duffel inventory when the Duffel API token is configured. Test mode is for integration testing; it should not be treated as guaranteed real-world fare accuracy.

Start with route + date

After the route and date are understood, you can continue with a short follow-up instead of repeating everything.

Airports, cities, and countries

Duffel ultimately needs airport/city identifiers. IOOK accepts common 3-letter IATA codes such as DEL, JFK, LHR, PEK, or PVG. If somebody says only a country such as “China,” IOOK should ask for a specific city or airport rather than pretending the country name is an airport code.

Selecting a result

Flight cards can show airline, route, cabin, stops, duration, segments, and fare. Choosing a flight moves the request toward the PORUS confirmation boundary.

Can IOOK issue a real ticket today?

No. The current beta deliberately stops before real-money ticket issuance. Traveller profiles, fare revalidation, explicit PORUS approval, provider-profile linking and gated Duffel TEST orders are now implemented. Live provider activation, customer-money execution and real ticket issuance remain intentionally locked before public production use.

People, places, context, tasks, and history.

Memory turns repeated context into something you can inspect. IOOK can remember explicitly mentioned entities such as people, companies, doctors, clinics, vendors, manufacturers, clients, employees, and places. The current beta does not try to infer private relationships or hidden personal facts from a name alone.

What happens when you click a memory?

A Memory profile can show the entity’s mention count, related open tasks, completed/history items, and an AI-generated “Before you talk” brief. The brief is supposed to summarize the actual task/history information IOOK has, not invent motives, relationships, deadlines, or facts.

Why Memory matters

The long-term purpose of Memory is not simply to collect names. It is to make IOOK context-aware enough that you do not have to reconstruct the history of a person, project, place, or recurring situation every time.

The permissioned action layer.

PORUS stands for Personal Orchestrator for Reliable and Uncomplicated Services. Its job is to execute approved actions for IOOK. That distinction matters: understanding a request is not the same as being allowed to spend money or make a booking.

Adding a payment method

In the current India-first beta, PORUS opens a Razorpay-hosted checkout/test flow. Sensitive payment entry is intended to occur in the provider’s secure interface rather than through an IOOK card-number form.

What IOOK should retain

IOOK should retain only safe references or metadata needed to identify a payment method, such as network, provider token/reference, or masked last digits. It should not persist raw PAN, CVV, UPI PIN, or online-banking passwords.

Explicit approval

A flight may be prepared by IOOK, but PORUS is supposed to ask for a separate authorization before execution. Even when payment credentials are tokenized, the bank/payment network may still require OTP, 3-D Secure, UPI authorization, or another form of customer authentication.

Real payments today

Real-money execution remains locked in the beta. Razorpay Test Mode can validate integration behavior without moving real money. Authenticated IOOK accounts, provider-profile linking, spending controls, step-up confirmation and execution receipts are now implemented. Live payment enablement still requires production-provider activation, compliance review and a controlled public rollout.

The security model IOOK is aiming for.

Security is not a single switch. IOOK separates different classes of data and tries to keep the most dangerous credentials outside the IOOK application wherever possible.

No product should claim to be “unhackable.” A stronger design principle is to minimize what sensitive data IOOK receives in the first place, separate customer data by user, encrypt sensitive information, restrict production access, keep audit logs, and use regulated providers for regulated operations.

Your private workspace now follows your IOOK account.

What needs to happen before production-scale use?

IOOK now has authenticated users, Row Level Security, normalized Tasks, Settings, and Memory. Accounts, traveller data, flight history, and PORUS approval history are the next data domains to normalize. Payment tokenization, production banking partnerships, notifications, and mobile delivery remain later production layers.

What is working, what is sandbox, and what is planned.

Examples that show how IOOK is meant to be used.

Inbox / life admin

Accounts

Flights

Memory

PORUS

When something does not work.

“The website still looks like the old version.”

Check GitHub first: make sure you replaced app.py, not a similarly named file such as aap.py. Then in Render confirm the live deploy corresponds to the latest Git commit. Hard-refresh the browser afterward.

“AI connected” is missing.

Check the OpenAI environment variables in Render. API billing is separate from a ChatGPT subscription, so API credits/billing must also be active.

Flights returns a provider error.

Verify the Duffel token and Test Mode status. If the location is a country, give a city or IATA code. If Duffel itself rejects a test offer, try another route/date because sandbox inventory can be unusual.

PORUS says payment is not connected.

Verify RAZORPAY_KEY_ID and RAZORPAY_KEY_SECRET in Render. Test and live credentials must not be mixed.

Setu gives 403 / KYC errors.

The AA production path has regulatory onboarding requirements. A Setu sandbox credential does not by itself make IOOK a production FIU. Complete only legitimate onboarding steps; do not select a regulator licence the company does not have.

Currency default is wrong.

Use the currency selector under the IOOK logo. Auto uses browser timezone first, then locale. A manual selection overrides Auto for that browser.

My data disappeared.

Tasks, Settings, and Memory now live in the signed-in private Supabase database. Accounts and PORUS history still use the authenticated private cloud-state layer until their normalized migrations. If something appears missing, verify you are signed into the same IOOK account and that the database sync indicator is healthy.