The 'single-endpoint' package helps you to call get API without creating multiple endpoints in your app.
Self-hostable proxy that pools multiple free-tier Gemini API keys behind a single endpoint with OpenAI and Anthropic dialect support
Resource enumerate is a special case API call that returns the interface of the API code in a single endpoint
WebSocket-based Model Context Protocol broker. Aggregates multiple MCP providers behind a single endpoint with stdio, SSE, and Streamable HTTP client transports.
Single endpoint server
A library support development single endpoint api.
Help you maintain a single endpoint api with dynamic handlers.
MCP aggregator: multiple upstream MCP servers behind a single endpoint with per-user OAuth.
MCP server that resolves Apifox APIs by URL via single-endpoint export — clean YAML, no full-project pull.
HTTP library for batched RPC calls and real-time server-push over a single endpoint.
A single endpoint to several github statistics.
MCP aggregator - connect multiple MCP servers through a single endpoint
deduplicate multiple http request to a single endpoint
A library support development single endpoint api (client).
Library to combine multiple files to a single endpoint, serving a single file.
Library to combine multiple files to a single endpoint, serving a single file.
Aggregate multiple MCP servers into a single endpoint with visual management
[](https://www.npmjs.com/package/@aws-sdk/middleware-bucket-endpoint) [](http
MCP hub/aggregator server — expose multiple MCP servers through a single endpoint
JSON object-based single-endpoint server API for JavaScript
Octokit plugin adding one method for all of api.github.com REST API endpoints
Shared TypeScript definitions for Octokit projects
[](https://www.npmjs.com/package/@aws-sdk/middleware-endpoint-discovery) [
A Rust-based local helper / proxy for Codex CLI traffic with multi-provider routing, usage-aware switching, filtering, and session helpers.
The Rust SDK for HarperDB
A mountable Rails engine that provides a configured, authenticated JSON briefing endpoint for AI agents to consume app data.
JsonapiResponses simplifies API response handling by allowing multiple response formats from a single endpoint, improving performance and reducing endpoint duplication
Fiveapples is a fully opensource and standalone OData + openui5 demo app. It runs a sqlite database, serves it as a Safrano based OData endpoint and additionally serves the openui5 demo app itself, all in a single ruby process.
llm.rb is Ruby's most capable AI runtime. It runs on Ruby's standard library by default. loads optional pieces only when needed, and offers a single runtime for providers, agents, tools, skills, MCP, A2A (Agent2Agent), RAG (vector stores & embeddings), streaming, files, and persisted state. As a bonus, llm.rb is also available for mruby. It supports OpenAI, OpenAI-compatible endpoints, Anthropic, Google Gemini, DeepSeek, xAI, Z.ai, AWS Bedrock, Ollama, and llama.cpp. It also includes built-in ActiveRecord and Sequel support, plus concurrent tool execution through threads, tasks (via async gem), fibers, ractors, and fork (via xchan.rb gem).
Diggr is a ruby wrapper for the Digg API. Diggr strives to remain consistent with the Digg API endpoints listed here: http://apidoc.digg.com/CompleteList. Endpoints are created in Diggr with method calls. Each node in an endpoint becomes a method call and each node which is an argument becomes an argument to the previous method. As an example, the following endpoint /user/{user name} in which the user name is "johndoe" would be created with this Diggr call: diggr.user("johndoe") To send the request to the Digg API and retrieve the results of the call, Diggr requests are terminated in one of two ways. 1. Using the fetch method. By ending your request with the fetch method, your result will be returned to you. If the request is singular, you will receive a single object as a response. If the request is plural, you will receive a collection of objects stored in an array. 2. Using any Enumerable method. In this case, it is unnecessary to use the fetch method. See the synopsis for examples of each of these types of calls. Options such as count or offset can be set using the options method and providing a hash of arguments. See synopsis for more information. Note: In an effort to remain consistent with the Digg API, some method names do not follow the ruby idiom of underscores. Although somewhat ugly, this allows a user to read the Digg API and understand the exact methods to call in Diggr to achieve their desired results.
Diggr is a ruby wrapper for the Digg API. Diggr strives to remain consistent with the Digg API endpoints listed here: http://apidoc.digg.com/CompleteList. Endpoints are created in Diggr with method calls. Each node in an endpoint becomes a method call and each node which is an argument becomes an argument to the previous method. As an example, the following endpoint /user/{user name} in which the user name is "johndoe" would be created with this Diggr call: diggr.user("johndoe") To send the request to the Digg API and retrieve the results of the call, Diggr requests are terminated in one of two ways. 1. Using the fetch method. By ending your request with the fetch method, your result will be returned to you. If the request is singular, you will receive a single object as a response. If the request is plural, you will receive a collection of objects stored in an array. 2. Using any Enumerable method. This works only on plural requests. In this case, it is unnecessary to use the fetch method. See the synopsis for examples of each of these types of calls. Options such as count or offset can be set using the options method and providing a hash of arguments. See synopsis for more information. Note: In an effort to remain consistent with the Digg API, some method names do not follow the ruby idiom of underscores. Although somewhat ugly, this allows a user to read the Digg API and understand the exact methods to call in Diggr to achieve their desired results.
Oddjob is a simple command line driver web server, written in ruby and utilizing ruby's built in web server webrick. It is meant to be a test and development tool, suitable for static content from a local directory. Oddjob also provides basic file upload capabilities (single or multi-file upload). This includes the ability to save uploaded files locally. As a stand alone application the server is quick and convenient application for web developers working with static files. Or get a copy of the source and add in new endpoints for simple tests as needed.
Diggr is a ruby wrapper for the Digg API. Diggr strives to remain consistent with the Digg API endpoints listed here: http://apidoc.digg.com/CompleteList. Endpoints are created in Diggr with method calls. Each node in an endpoint becomes a method call and each node which is an argument becomes an argument to the previous method. As an example, the following endpoint /user/{user name} in which the user name is "johndoe" would be created with this Diggr call: diggr.user("johndoe") To send the request to the Digg API and retrieve the results of the call, Diggr requests are terminated in one of two ways. 1. Using the fetch method. By ending your request with the fetch method, your result will be returned to you. If the request is singular, you will receive a single object as a response. If the request is plural, you will receive a collection of objects stored in an array. 2. Using any Enumerable method. In this case, it is unnecessary to use the fetch method. See the synopsis for examples of each of these types of calls. Options such as count or offset can be set using the options method and providing a hash of arguments. See synopsis for more information. Note: In an effort to remain consistent with the Digg API, some method names do not follow the ruby idiom of underscores. Although somewhat ugly, this allows a user to read the Digg API and understand the exact methods to call in Diggr to achieve their desired results.
The PostBoost REST API lets you publish, schedule, and analyze social media posts across 8+ platforms from a single integration. No OAuth apps to maintain — PostBoost handles platform authorization for you. ## Base URL All workspace-scoped endpoints are prefixed with `/{workspaceUuid}`. Panel/admin endpoints are prefixed with `/panel`. ## Authentication All requests require a Bearer token in the `Authorization` header. Generate tokens in your PostBoost dashboard under **Settings → Access Tokens**. ``` Authorization: Bearer YOUR_API_TOKEN ```
Brings the stimulus_grid data-grid into Rails as a first-class engine. Provides ApplicationGrid for declaring columns server-side; cell-grained Turbo Stream actions (cell, cell-confirm, cell-revert, row-insert-sorted, row-remove, bulk); a single PATCH endpoint for cell mutations with optimistic-id reconciliation; and importmap-pinnable JS for both the grid and the live-sync layer.
Mycel is a single-file, pure-Ruby RPC library built around perfect role symmetry: once a TCP connection is established, either side can invoke any method exposed by the other — there is no client and no server, only peers. Each connection is one hypha; each Endpoint is a node in your own programmable mycelial mat. Layered architecture (Framing / Transport / Channel / RPC), pluggable codec, backpressure, pluggable executor, and zero monkey-patching of Ruby standard classes.
Turbo Overlay turns any controller action into a modal- or drawer-friendly endpoint. A single stack container on the host page receives streamed overlays; the gem detects overlay requests, swaps in an overlay layout, exposes a request variant for view-level customization, and ships a custom turbo-stream action plus Stimulus controllers for opening, stacking, and closing overlays. Themes for Tailwind, Bootstrap 5, Bootstrap 3, and plain CSS are installable via generator.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.