NeonAI API Proxy
Proxies API calls to consolidate usage to a single point and allow for caching of API data.
Request Format
API requests should be in the form of a dictionary. The service requested should be specified as service and the
remaining data will be passed to the handle_query method of the requested service as kwargs.
Example Wolfram|Alpha Request:
{ "service": "wolfram_alpha", "query": "how far away is Rome?", "api": "simple", "units": "metric", "ip": "64.34.186.120" }
Response Format
Responses will be returned as dictionaries. Responses should contain the following:
status_code- Usually contains the HTTP status code from the requested API,-1should be used to specify any other errorscontent- Usually contains the HTTP content (bytes) from the requested API, but may include a string message for errors.encoding= Usually contains the HTTP content encoding if content is the byte representation of a string, may beNone
Docker Configuration
When running this as a docker container, the XDG_CONFIG_HOME envvar is set to /config.
A configuration file at /config/neon/diana.yaml is required and should look like:
MQ:
port: <MQ Port>
server: <MQ Hostname or IP>
users:
neon_api_connector:
password: <neon_api user's password>
user: neon_api
keys:
api_services:
alpha_vantage:
api_key: <Alpha Vantage Key>
open_weather_map:
api_key: <OWM Key>
wolfram_alpha:
api_key: <Wolfram|Alpha Key>
For example, if your configuration resides in ~/.config:
export CONFIG_PATH="/home/${USER}/.config"
docker run -v ${CONFIG_PATH}:/config neon_api_proxy
Note: If connecting to a local MQ server, you may need to specify
--network host
Metadata
Release files for neon-api-proxy 0.7.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| neon-api-proxy-0.7.0.tar.gz | 17.2 kB | Without provenance | Details for neon-api-proxy-0.7.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| neon_api_proxy-0.7.0-py3-none-any.whl | Python 3 | none | any | Details for neon_api_proxy-0.7.0-py3-none-any.whl |
Total release size: 62.9 kB
Release files / neon-api-proxy-0.7.0.tar.gz
| Download URL | neon-api-proxy-0.7.0.tar.gz |
|---|---|
| Size | 17.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7c9c11e23c601e85da63d808c143df7d0a29b9b3cd9365fd1ec6853432f848f5
|
|
BLAKE2b-256 checksum How to use checksums |
6cb2ba0d33f9cbb542ce8894eb270d450c67fe7f61c845b39bde14706f13ce87
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.12.6
|
Release files / neon_api_proxy-0.7.0-py3-none-any.whl
| Download URL | neon_api_proxy-0.7.0-py3-none-any.whl |
|---|---|
| Size | 45.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
4a2e7b06a366673643440ff95328dfeddcfd2d29dc32d3daeb6769ae26958ad2
|
|
BLAKE2b-256 checksum How to use checksums |
b8e2dab96fda2109def8b001bea3e86e48deb56752c8d582f56f70cde53fc0ad
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.12.6
|
Security for neon-api-proxy 0.7.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.