Journal Intelligence
Real-Time Data from OpenAlex & Crossref
G1 Journal Matcher connects to the OpenAlex and Crossref APIs for live journal metrics, publication trends, and editorial profiling — replacing static knowledge with real-time data.
What is Journal Intelligence?
Diverga's G1 Journal Matcher uses six specialized MCP tools to query live bibliometric data from OpenAlex and Crossref. A checkpoint-based pipeline guides researchers from abstract analysis through final journal selection with full bilingual support.
Free API access — no keys needed
6 specialized MCP tools
Checkpoint-based pipeline
Bilingual support (EN/KO)
4-Stage Matching Pipeline
Each stage builds on the previous, guiding you from raw abstract to a final journal choice backed by live data.
Research Field Analysis
5 minAnalyze the paper abstract to identify the research field and derive candidate search terms
Data Collection
2-3 minParallel API calls to OpenAlex and Crossref collect live metrics for all candidate journals
Priority Selection
CheckpointCheckpoint — user selects ranking criteria (impact factor, OA status, APC, turnaround)
Journal Selection
CheckpointCheckpoint — compare finalists side by side with real-time data and make the final choice
6 MCP Tools
Each tool targets a specific dimension of journal intelligence, giving you granular control over which data to fetch.
journal_search_by_field
Search journals by research field, sorted by total citations
journal_metrics
h-index, 2-year average citations, works count, open access status, APC
journal_publication_trends
Works and citations per year for a configurable number of years
journal_editor_info
Top authors by publication count — editorial board profiling
journal_compare
Compare 2–5 journals side by side across all key metrics
journal_special_issues
Recent themed publications — identify active special issue opportunities
Email Configuration
OpenAlex rewards polite API callers. Providing an email address places your requests in the "polite pool," which receives higher rate limits and priority routing.
OPENALEX_EMAIL env var
Set once in your shell profile — applies globally
.omc/config.json
Per-project setting in your Diverga config file
No email
Still works, but subject to stricter rate limits
- Polite pool: higher rate limits and priority routing
- Email is sent only in the User-Agent header — never stored
- Applies to all six OpenAlex-backed MCP tools automatically
Learn More
Explore detailed documentation for each component:
Ready to Start Matching Journals?
Use Diverga's G1 Journal Matcher to find the best-fit journal for your paper with live bibliometric data — in minutes.