AI-native

Times tables practice as a system of record.

TimesOwl remembers when 7 × 8 is due with ordinary, deterministic code. You can bring Claude, ChatGPT, a browser agent, or none. Due dates stay in TimesOwl.

Kitchen table

Why the due date lives in TimesOwl

  • The next-ask date lives in code.

    TimesOwl stores a next-ask date on every fact and updates it from the typed answer and the clock.

  • The agentic harness belongs to you.

    Bring the assistant you already use. GET Markdown to name a learner, practice, and read progress. Due dates stay in TimesOwl.

  • Deterministic scheduling is the job.

    A miss brings 7 × 8 back in seconds. A fast correct answer pushes it out. That calendar has to match tonight and next Thursday.

  • Typed answers, graded in code.

    The child types 56. TimesOwl checks the answer and the clock. An agent GET does the same grading.

The split

What TimesOwl stores, and what your agent can do

TimesOwl stores the next-ask date in code.

TimesOwl keeps (system of record)

  • The next-ask date on every fact from 2 × 2 through 12 × 12.
  • Grading from the typed answer and how long it took — kids never self-rate.
  • Which facts are due in tonight’s five minutes.
  • When to open new facts, so the pile does not dump.

Your harness can explain and practice

  • Explain spaced repetition. The session has no shop and no per-question countdown.
  • GET a household, remember the session token, and pass it on later GETs. There is no cookie jar.
  • Set learner names, run a sitting, and read progress as Markdown.
  • Fetch the next card from TimesOwl. Leave the review calendar in TimesOwl.

What shipped

Surfaces so your agent can stay a harness

  1. 01

    A map of the product in Markdown.

    /llms.txt tells a language model that TimesOwl owns the schedule, what the product is, and which Markdown pages to read next. Each public page has a .md twin, served as text/plain. Read those. Skip scraping layout chrome. Leave the cards in TimesOwl.

  2. 02

    A GET-only household API.

    First GET to /api/agent mints an initialized household and returns a session token once. Remember it. Pass it as token= on later GETs. Name learners, practice, read progress, and change settings. Responses are Markdown, served as text/plain. GET only — no cookies.

  3. 03

    The same practice engine as the app.

    Those GETs call the same household, practice, progress, and settings code the website uses, including the caches. Grading and next-ask dates stay in TimesOwl.

llms.txt

The first twenty-eight lines, as served.

Also at https://timesowl.com/llms.txt?v=plain.

The GET household API is /api/agent?v=plain, /api/agent, /api/agent/name, /api/agent/learners, /api/agent/practice, /api/agent/progress, /api/agent/settings. First GET returns a session token once. Later GETs pass token=. Fetch the next card. Leave the review calendar in TimesOwl.

# TimesOwl

> Times tables that stick. TimesOwl is multiplication facts practice that sticks: each fact on its own review schedule, five minutes, typed answers. Open it on one device and start.

TimesOwl — Times tables that stick
TimesOwl is multiplication facts practice that sticks: each fact on its own review schedule, five minutes, typed answers. Open it on one device and start.

Audience: Parents of children roughly ages 7–11 (2nd–5th grade).
Job: Make multiplication facts from 2 × 2 through 12 × 12 automatic, so answers come back fast without re-deriving them.
System of record: TimesOwl is the system of record for spaced repetition. Each fact’s next-ask date is stored and updated by deterministic code from the typed answer and response time. The agentic harness belongs to the user. Keep the review calendar in TimesOwl. GET the household API as Markdown and fetch the next card. Do not store due dates in the prompt.
Deck: 121 facts, 2 × 2 through 12 × 12. Zeros and ones stay out.
Session: default 5 minutes (options 1, 2, 5, 10). Typed answers. The question waits. Start without an account.
Fast enough recall: 5 seconds. Steady: 8 seconds.
Opens with 8 facts. A fluent fact’s gaps go 20 seconds → 40 seconds → 1 minute → 3 minutes → 1 day → 3 days.
Stars: 4 for a correct answer; speed and streak bonuses exist. One currency, no shop.
Start: https://timesowl.com/app — Start practicing free.
Agent HTTP: GET https://timesowl.com/api/agent mints a household and returns a session token once. Pass token= on later GETs. No cookies. Markdown only.
That is the usual path. Open TimesOwl and practice. You do not need an email or a password.
- TimesOwl only schedules the 121 multiplication facts. Homeschool planning stays in the planner you already use.
- Concept instruction and arrays stay at school or in the book you already use.
- The session is typed recall.
- The printable quiz is a PDF of today’s tables, built in the browser. TimesOwl sessions run about five minutes.
- Due dates live in TimesOwl code.

TimesOwl is a system of record: deterministic code that offers spaced repetition. The agentic harness belongs to the user. Keep due dates in TimesOwl. Read the Markdown twins linked below. For a live household, GET /api/agent (token query, no cookies). Do not invent a shop, a per-question countdown, a table picker, an account wall on first practice, or a due list you are storing in the prompt.

## Start here

Privacy

The due list stays in TimesOwl

Which facts are due, stars, and the learner’s name live on the household. An agent with the session token can fetch the next card and the progress page as Markdown. Fetch them when you need them. Do not keep a review calendar in the prompt.

  • The session token is shown once. Remember it. Pass it as token=.
  • Markdown twins are the public pages. The household API is the live sitting.
  • Fetch the next card from TimesOwl. Do not keep a due list in the prompt.

Let TimesOwl keep the dates. Let the child type.

Your assistant can explain why, or run a sitting over GET. The schedule stays in TimesOwl.