Oak API

Turn Oak Curriculum API content into age-appropriate learning flows, endpoint maps, or implementation guidance without losing compliance and learner-safety constraints.

Standards snapshot (March 2026)

• Prioritize learner safety, age fit, and clarity before clever product mechanics.
• Treat Oak content as a factual backbone, not something to dump verbatim into the chat.
• Keep compliance explicit: attribution, rate limits, API-key handling, and no implied endorsement.
• Default to recommendations and flows first; move into code only when the user asks for implementation.

Philosophy

• Learner safety and clarity outrank novelty.
• Use Oak as structured curriculum evidence, not as copy to repeat wholesale.
• Keep outputs actionable for tutors, parents, teachers, or app builders.