Agragene · Authentication Profile
Agragene Authentication
Authentication
Agragene publishes no REST/GraphQL API and therefore no securitySchemes. The only callable surface is the site MCP endpoint, which is ANONYMOUS: an unauthenticated JSON-RPC initialize and tools/list both returned HTTP 200 on 2026-09-12, and the company's own llms.txt states "No authentication required to connect to the MCP endpoint". A per-session visitor token exists one level down, minted by the GenerateVisitorToken tool and required only as an argument to CallWixSiteAPI / ExecuteWixAPI; it is not a credential a consumer registers for.
Agragene declares 2 security scheme(s) across its OpenAPI definitions.
AgricultureAgtechBiotechnologyGene EditingPest ControlSustainabilityFood and BeverageLife SciencesCompany
Methods:
Schemes: 2
OAuth flows:
API key in:
Security Schemes
none
bearer-session
Source
Authentication Profile
Work with this as data
Every security artifact here is available over the APIs.io API and to AI agents over MCP.