Repository inventory

upsurgeio/akhrot

Skills indexed from this repository, with install-style signals scoped to the repo.
1 skills1 GitHub stars0 weekly installsGitHubOwner profile

Overview

This skill integrates with Akhrot to manage OAuth tokens and API keys for external services like Gmail, GitHub, Slack, OpenAI, Stripe, and more. It centralizes credential retrieval and session creation so you can fetch valid credentials and call provider APIs directly. The skill keeps tokens refreshed and exposes lightweight endpoints to check connected providers and create OAuth sessions for new connections.

How this skill works

Use your Akhrot API key as the user identity in the Authorization header. First query the connection summary or provider details to see what’s available. Fetch access tokens or API keys from /tokens/fetch, or create an OAuth session with /oauth/sessions to get a user authorization URL. After retrieving credentials, call the provider’s native API directly using the returned token or key.

When to use it

  • You need a central place to fetch OAuth access tokens or API keys for multiple providers.
  • You want tokens that auto-refresh without managing refresh logic yourself.
  • You must create OAuth authorization flows for users and obtain consent URLs quickly.
  • You prefer calling provider APIs directly while delegating credential storage to Akhrot.
  • You need programmatic checks of which providers a user has already connected.

Best practices

  • Always include Authorization: Bearer {Akhrot_API_KEY} on Akhrot requests; this key identifies the user.
  • Check the connection summary before fetching tokens to avoid unnecessary calls.
  • Handle error codes (UNAUTHORIZED, INTEGRATION_NOT_FOUND, TOKEN_EXPIRED, RATE_LIMITED) gracefully and show actionable messages.
  • Send users to the /oauth/sessions url for consent; do not attempt to authorize on their behalf.
  • After fetching credentials, use the provider’s native SDK or REST endpoints and treat Akhrot tokens like any other access token.

Example use cases

  • Fetch a Gmail access token and list the user’s recent messages via the Gmail API.
  • Create an OAuth session for Google Drive so a user can grant file access to your app.
  • Retrieve an OpenAI API key from Akhrot and call the OpenAI completions or embeddings endpoints.
  • Obtain a Stripe API key stored in Akhrot to create a payment intent from your backend.
  • Use Telegram MTProto credentials (apiId/apiHash/session) returned by Akhrot with Telethon or gramjs.

FAQ

Your Akhrot API key in the Authorization header identifies the user; there is no separate userId parameter.

Do I need to refresh tokens manually?

No. Tokens returned from /tokens/fetch are auto-refreshed by Akhrot when expired whenever possible.

What if a provider isn’t connected?

Create an OAuth session via /oauth/sessions to get an authorization URL and have the user complete the consent flow.

1 skills

More from this maintainer
Other repositories and skills published under the same GitHub owner.
Skills library
Jump back to the full directory or explore grouped topics.
Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational