Register as an e-Tag agent with the relevant e-Tag authority service (typically your ISOs/RTOs' designated authority or a commercial e-Tag platform such as OATI webSmartTag); obtain digital certificates required for signed XML message submission.
Construct the e-Tag XML payload per NAESB WEQ-012 (Electronic Tagging Functional Specification); the tag must include: tagID (unique across the submitting entity), transactionType ('PURCHASE' or 'SALE'), contractNumber, marketSegments (energy source and sink with MW quantities), and physicalSegments (transmission path with TSR numbers from OASIS).
Submit the e-Tag via POST to the authority service's endpoint with the XML body and appropriate authentication headers; the authority service validates the tag structure and forwards approval requests to each transmission provider listed in the physical segments.
Monitor approval status by polling the authority service's tag status endpoint with the tagID; each physical segment provider must approve (or reject/conditionally approve) the tag — a tag is only dispatchable when all segments reach 'APPROVED' status.
For tags requiring curtailment adjustments during the operating hour, submit a tag amendment (tagType='AMENDMENT') with the modified MW quantity and the original tagID as the reference; amendments require re-approval from affected segment providers.
Submit a tag termination request before the end of the trading day for unused capacity; unreturned approved tags may result in transmission service charges even if the energy was not dispatched.
Known gotchas
E-Tag XML schemas are defined in the NAESB WEQ-012 specification (currently version 1.8.x); the specification is a paid NAESB document — implementers must purchase it, and free or unofficial schema copies may be outdated or incomplete.
Physical segment transmission service reservations (TSRs) must be confirmed in the OASIS system before submitting the e-Tag; attempting to submit a tag referencing a TSR that is not yet confirmed will result in rejection by the authority service.
E-Tag approval workflows are time-sensitive: NERC requires pre-approval before the tag's operating hour — late submissions may be rejected by transmission providers even if the tag is otherwise valid; check the applicable tariff's tag submission deadline (typically 20 minutes before the operating hour).
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp