{
  "version": "1.0",
  "type": "repository",
  "interval": "day",
  "date": "2026-02-11",
  "generatedAt": "2026-05-13T23:41:49.530Z",
  "sourceLastUpdated": "2026-05-13T23:41:49.530Z",
  "contentFormat": "markdown",
  "contentHash": "3b0bd59ad5ababae83ffb31c019084173c8f13b04bfe8f9684e0aa9a5a6d2876",
  "entity": {
    "repoId": "elizaos-plugins/plugin-jupiter",
    "owner": "elizaos-plugins",
    "repo": "plugin-jupiter"
  },
  "content": "# elizaos-plugins/plugin-jupiter Daily Update (Feb 11, 2026)\n## OVERVIEW \nThe day saw a significant new pull request to switch the Jupiter plugin from `lite-api` to `api.jup.ag` with API key authentication, indicating a move towards more robust API integration.\n\n## KEY TECHNICAL DEVELOPMENTS\n\n## NEWLY OPENED PULL REQUESTS\nA new pull request, [#4](https://github.com/elizaos-plugins/plugin-jupiter/pull/4), was opened to switch the plugin's API integration from `lite-api` to `api.jup.ag`, incorporating API key authentication for enhanced security and functionality.\n\n## CLOSED ISSUES\n\n## NEW ISSUES\n\n## ACTIVE ISSUES\nDiscussion continued on [#6490](https://github.com/elizaos-plugins/plugin-jupiter/issues/6490), a feature request to support custom OpenAI endpoint URLs for the OpenAI provider. A new comment from arcaela emphasized the importance of this feature for enabling compatibility with various OpenAI-compatible third-party services, such as Arko Studio, which offers free API keys. The comment highlighted that only the `base_url` would need to be changed to integrate such services."
}