i2-api
Skill30 starsChanged 50 days agoBSD-2-ClauseView on GitHub
DEPRECATED. The legacy AmSC i2-api (api.i2-core.american-science-cloud.org) is retired in favor of the Model Access Gateway (MAG). Use this skill only to migrate an existing i2-api setup; for all LLM work use the amsc-mag skill. Trigger on i2 API, i2-core, AMSC_I2_API_KEY, or API Key Manager.
- Reads credentials
In this repository30 other files it gives its agents.
- skills/academy/agents.mdAGENTS.md
- academySkill
- amsc-data-movement-apiSkill
- amsc-magSkill
- amsc-python-clientSkill
- globus-computeSkill
- iri-apiSkill
- skill-explorerSkill
- croissant-validatorSkill
- datacard-generatorSkill
- hdmf-schema-builderSkill
- skill-creatorSkill
- well-convertSkill
- card-eval-updaterSkill
- agentic-vulnerabilities-scanSkill
- ai-fingerprintSkill
- battleprintSkill
- fingerprintingSkill
- uncertainty-quantificationSkill
- uq-metrics-evaluatorSkill
- skill-searchSkill
- auroraSkill
- frontierSkill
- pbsSkill
- perlmutterSkill
- slurmSkill
- literature-searchSkill
- multi-agent-systemsSkill
- gkeyllSkill
- gs2Skill
The file
Files
i2-api (deprecated)
The legacy i2-api is deprecated. Do not use it for new work, and do not generate code that targets it. Existing i2-api users must migrate to the AmSC Model Access Gateway (MAG). Use the amsc-mag skill for everything LLM-related.
Old to new
| Legacy i2-api | MAG | |
| Host | api.i2-core.american-science-cloud.org | https://mag.genesis.americansciencecloud.org |
| Login | AmSC Google login | Ping Identity (AmSC IdP) |
| Credential | API key from "API Key Manager" | Personal Access Token (PAT) |
| Env var | AMSC_I2_API_KEY | AMSC_TOKEN |
| Where to create | i2-api web UI | https://my.amsc.energy.gov/dashboard -> project -> Personal Access Tokens -> Generate PAT |
| Requirement | any key | approved project with a MAG allocation |
Migration steps:
- Generate a PAT (short-lived; a 401 means generate a new one) and export
AMSC_TOKEN. - Replace the base URL with
https://mag.genesis.americansciencecloud.org/v1. - Replace
AMSC_I2_API_KEYwithAMSC_TOKENin code and shell config. - Re-check model names against
GET /v1/models; the MAG uses<base>[:<mod>]...[@<provider>]model strings. - For Claude Code, replace the old exported environment with the scoped
claude-amscfunction inamsc-mag/references/claude-amsc.sh.
See the amsc-mag skill for details.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.