PUBLIC TOOL STREET · JEE + NEET

Use the instrument. Read its boundary.

Each door is labelled by its real operating state. Live tools wait for source-backed responses; decision-only tools explain their rules; preview doors cannot imitate a completed result.

START HEREOne reviewed public question
Public question
PUBLICJEE
loading
Selecting an approved question

The public pool is checked before anything is shown.

PUBLIC TOOL LAWNo source, no result.

Network failure, empty coverage, contract mismatch, withdrawal, and rate limits render explicit states. No fixture or remembered result replaces them.

S1 · SIX PUBLIC DOORS

Start with the problem in front of you.

Tools are grouped by the action they can complete now, not by a large product taxonomy.

T01LIVE API

Sample question

Answer one reviewed JEE or NEET question and receive the result only after server-side submission.

  • No score prediction
  • No private practice history on the website
Answer a question →
T02LIVE API

College predictor

Put an existing rank against the public cutoff projection and inspect the source and limitations.

  • Rank input only
  • Planning aid; no assured seat outcome
Check a rank →
T03LIVE API

Cutoff explorer

Search the canonical college index, select a college, and inspect available cutoff rows.

  • Only published rows appear
  • Official counselling rules remain authoritative
Search cutoffs →
T04LIVE API

Chapter map

Browse the exam-scoped concept graph by subject and chapter without an unscoped fallback.

  • Topic counts are not mastery scores
  • Empty source states remain empty
Open the map →
T05DECISION ONLY

Preparation route finder

Choose the problem in front of you and receive a next public action—not an invented paid-plan recommendation.

  • No price or entitlement advice
  • Not a personalised study plan
Find a route →
T06PREVIEW

Grading boundary

Inspect what a public grading workflow would require before submitting work in the app.

  • No fake grade
  • No live public grading API yet
Inspect grading →
S2 · METHOD

Three checks before any public outcome.

01

Validate the request

Unsupported exams, percentile conversion, incomplete searches, and malformed answers stop before result rendering.

02

Validate the source

The API envelope must carry source identity, state, freshness, methodology, coverage, and a request ID.

03

Carry only useful context

App entry can carry the touched public object through continuity. Exact restoration remains separately gated until app proof exists.