Overview
SAIMSARA institutional access is designed for libraries, universities, hospitals, research organizations, and institutional AI teams that need access to the published SAIMSARA paper layer without purchasing papers one by one.
Access can be activated for a specific institutional email address or for an approved email domain. Users log in with the normal SAIMSARA email/PIN workflow; if their email is covered by an active institutional pass, full papers open automatically.
What is included
- All published SAIMSARA papers: full human-readable article access across the published journal layer.
- Machine-readable Evidence JSON: downloadable structured evidence object included with full paper access where available.
- Email or domain-based access: activation for named institutional emails or approved institutional domains.
- Institutional account status: logged-in users can see whether all-paper institutional access is active.
- Receipts and invoices: payment confirmation is available; formal invoices can be issued on request.
- Library-friendly setup: no SSO is required for the initial version; users authenticate by email/PIN.
Pricing
The following launch prices are indicative annual conditions. Final institutional terms depend on institution size, access scope, intended use, and whether commercial machine-readable reuse or expanded API access is required.
Founding small library / single department
Best for: Small libraries, individual departments, research groups, or hospital departments.
Includes: All published SAIMSARA papers, Evidence JSON downloads, named-email or domain-based access.
Standard university or hospital library
Best for: University libraries, hospital libraries, academic medical centers, and institutional research teams.
Includes: All published SAIMSARA papers, Evidence JSON downloads, institutional login, invoice on request.
Large institution / multi-campus / corporate
Best for: Large universities, multi-campus organizations, companies, or institutions with broader access needs.
Includes: Custom institutional scope, all-paper access, Evidence JSON downloads, agreed access domains or named users.
Consortium / commercial RAG / bulk JSON or API use
Best for: Consortia, commercial AI/RAG applications, bulk structured evidence use, or advanced API licensing.
Includes: Custom terms for machine-readable reuse, higher-volume access, API quotas, and integration support.
Conditions
| Condition | Description |
|---|---|
| Access period | Usually annual. Shorter or longer periods can be agreed individually. |
| Access method | Named emails or approved institutional email domains. |
| Paper scope | All published SAIMSARA papers available during the active access period. |
| Evidence JSON | Included with full paper access where the paper has a connected Evidence Object. |
| Redistribution | No public redistribution, mirroring, resale, or bulk republication unless separately agreed. |
| Commercial AI/RAG use | Requires a separate commercial or bulk machine-readable access agreement. |
Activation
- The institution contacts SAIMSARA with the requested access scope.
- SAIMSARA agrees annual conditions and invoice/payment details.
- Access is activated for named emails or an approved institutional domain.
- Institutional users log in with their email using the SAIMSARA email/PIN workflow.
- Full-paper access opens automatically while the institutional pass remains active.
Not included by default
- No unlimited Pro synthesis workflow: institutional paper access does not automatically include unlimited Search → Paper generation.
- No unlimited Evidence API: API quotas are separate unless included in a custom agreement.
- No bulk scraping: automated harvesting or mirroring requires explicit agreement.
- No clinical deployment license: SAIMSARA papers and evidence objects are research and information resources, not standalone clinical decision systems.
Request institutional access
To request institutional access, send the institution name, contact person, expected access scope, preferred activation method, and whether machine-readable reuse or API access is needed.