Use the full public feed during growth mode.
Open the console, download CSV/JSONL, or query the API without an account while we validate real demand.
Start free trial →大学データと最新の比較情報を読み込んでいます。数秒たっても切り替わらない場合は、 一度ページを再読み込みしてください。
daigakujoho.com turns university updates into a compact feed for AI agents, search products, education data tools, and RAG builders. The MVP focuses on time-sensitive, decision-relevant changes rather than a static school directory dump.
The paywall stays off, but the commercial contract is explicit: free evaluation now, AI-readable entry points now, and AI Data Proof Pack requests when a buyer wants evidence beyond the public feed.
Open the console, download CSV/JSONL, or query the API without an account while we validate real demand.
Start free trial →Use llms.txt, OpenAPI, JSONL, and filtered signals endpoints as a freshness layer for RAG or AI search.
Open llms.txt →This is not a subscription upsell. Pick a public proof pack first, then decide if the data asset is worth a deeper buyer conversation.
Request proof pack →This route keeps the public data room first, asks one integration question, and avoids private data-room or access promises from anonymous clicks.
Show Search Console, growth audit, and public change-page evidence first. Keep the public data room first; no SLA or paid access is promised from an anonymous click.
Request traffic proof →Ask one integration question: should the feed enter RAG, a search index, or an operator inbox first? Then package only public endpoints and sample output.
Request integration proof →Treat BtoAI as an asset-buyer proof pack, not a subscription upsell. Preserve public signals, source URLs, and operator evidence before any NDA step.
Request acquisition proof →This is the copyable handoff for a buyer or assistant who asks whether BtoAI is worth evaluating. It turns the open feed into one of three next actions without making it a subscription upsell.
source=btoai_data_buyer_brief / brief=btoai_data_buyer_brief / public proof first
Start from the console or public change pages, then export the same data only when you need it inside a spreadsheet, AI workflow, search index, or RAG pipeline.
Open a readable table first. No API client, no code, no setup.
Open console →Use CSV for spreadsheets, JSONL for RAG, JSON for product integrations.
Download CSV →Use the public changes page to see what the feed looks like as human-readable pages.
View changes →The current path is not a subscription push. It is proof that search demand, compare intent, and AI data consumption can turn daigakujoho into a measurable traffic and data asset.
Keep growing search pages first: Search Console clicks, impressions, and compare actions are the evidence that makes the site sellable.
View SEO proof →Let agents, RAG tools, and search products try the full structured feed before we decide whether paid access is worth turning on.
Download JSONL →Track demo runs, console opens, endpoint clicks, and partner emails separately from bot/API request volume.
Open buyer console →The first commercial wedge is not “sell an API”. It is “sell the time advantage of clean university change signals”.
Use the release feed as a freshness layer before recommending schools, deadlines, open campus visits, or admission changes.
Download JSONL →Filter high-signal updates by university, prefecture, signal type, and source confidence before contacting students or families.
Open console →Each signal includes source URLs, public summaries, confidence, timing fields, and university ids for downstream indexing.
View OpenAPI →The paywall is intentionally off now. Public users, AI crawlers, search products, and RAG builders can evaluate the complete feed before any named buyer agreement or private data-room discussion.
All release-ready signals are visible now
A buyer proof pack can summarize freshness and usage evidence
Full JSON fields, ids, source URLs, confidence, scores
A commercial agreement can later define private history and support
No artificial delay during the growth phase
Priority alerts should wait until buyer demand is explicit
Public pages, API, CSV, JSON, JSONL, llms.txt
API keys remain ready only for named partners or buyers
Each item includes type, scope, university match, source URL, confidence, relevance score, and why it matters for school selection.
The operating plan is simple: daily watch for urgent news, curated releases every three days, and a weekly digest for operators and builders. Low-confidence or inferred records stay out of the release until reviewed.
大学名に直接紐づく News、入試・学費・Open Campus の速報性が高い変化だけを先に検知します。
公式 Open Campus、学事暦、住まい支援、奨学金・学費関連をまとめて清洗し、AI が扱いやすい JSON にします。
前週の重要変化、大学別シグナル、review queue を短く要約し、公開データの更新価値を確認しやすくします。
The public endpoints expose the complete structured release for evaluation. API keys remain supported for the future paid mode, but current open access does not require authentication.
This is the non-engineer entry point: choose a useful query, run it in the browser, then decide whether the feed is worth exporting to an AI workflow, spreadsheet, or search index.
/api/btoai/signals?limit=3Run a query to preview current release data without opening an API client.
curl -s "https://daigakujoho.com/api/btoai/signals?scope=direct_university_news&limit=10"Use daigakujoho BtoAI Scout data as a freshness layer.
Task: Find Japanese university changes that may affect school selection this week.
Prioritize: admission_change, tuition, faculty_change, open_campus.
Return: university name, change type, why it matters, source URL, and confidence.The current goal is distribution: let users and AI systems experience the utility first. Buyer-facing monetization should start as a one-off proof pack, partner evaluation, or acquisition data-room path.
The code path still supports access codes, buyer sessions, API keys, and request emails. We keep them behind public proof-pack demand while the priority is growth, AI discoverability, and asset evidence.
The open feed is for evaluation, search, AI/RAG ingestion, and user discovery. Redistribution, resale, or commercial bulk republication can move into a separate agreement later.
Data consoleEmail [email protected]