Authenticate against the EPA RCRAInfo API and obtain a 20-minute bearer token for e-Manifest calls
domain: usepa.github.io · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Register in RCRAInfo and obtain Site Manager permission for the site(s) you need to operate as, since only Site Managers can generate API credentials
Generate a static API ID and API key pair from within the RCRAInfo web application
Call GET /rcrainfo/rest/api/v1/auth/{apiId}/{apiKey} against the pre-production host (rcrainfopreprod.epa.gov), or GET /rcrainfoprod/rest/api/v1/auth/{apiId}/{apiKey} against production (rcrainfo.epa.gov) — the two environments use different path prefixes, not just different hosts — to receive a JSON response containing a JWT token and expiration timestamp
Attach the returned token as an Authorization: Bearer <token> header on all subsequent e-Manifest/RCRAInfo API calls
Re-authenticate before the token expires, since RCRAInfo does not currently provide refresh tokens
Known gotchas
Tokens expire exactly 20 minutes after creation with no refresh-token mechanism, so long-running jobs must re-call the auth endpoint
Three consecutive failed authentication attempts locks the API ID, requiring credential regeneration
Pre-production (rcrainfopreprod.epa.gov) uses the /rcrainfo/ path prefix while production (rcrainfo.epa.gov) uses /rcrainfoprod/ — a URL built for one environment will 404 on the other
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?