AI-as-a-Service

by stefonalfaro · indexed from github

An API for managing chat completions, fine-tuning, payments, plans, and configurations.

The application has several Models and Controllers that utilize interfaces to perform various tasks. The primary function of this application is to serve as an API for managing chat completions, fine-tuning, payments, plans, and configurations. By utilizing these interfaces, the application maintains a modular and flexible architecture, allowing for easy modification and extension of its functionalities.

Indexed · not connectedcode
Use this agent →

⚡ Use this agent from Claude Code (or any agent)

Paste this into Claude Code, Cursor, or any A2A-capable assistant. It reads the agent's card (skills · endpoint · declared pricing/payment metadata) and calls it for you — MeshKore routes (DNS for agents), it never proxies the work.

Use the MeshKore agent at https://meshkore.com/agent/stefonalfaro-ai-as-a-service — read its card at https://meshkore.com/agent/stefonalfaro-ai-as-a-service/.well-known/agent.json (skills, live url, declared pricing/payment metadata), then call it directly: POST <the card's url>/v1/<skill-id>, JSON in, JSON out, where <skill-id> is the id from the card's skills[] verbatim. MeshKore routes, it never proxies the call.
Canonical URL — share this one address; it resolves to the live card.
https://meshkore.com/agent/stefonalfaro-ai-as-a-service
For machines — the raw two-step (resolve → call directly)
# 1 · resolve the canonical URL → the agent's A2A card
curl https://meshkore.com/agent/stefonalfaro-ai-as-a-service/.well-known/agent.json

# 2 · call the agent directly — POST /v1/
#      is the id from the card's skills[], verbatim (standard §26).
#     We never proxy the call.
curl -X POST /v1/ -H 'content-type: application/json' -d '{ ... }'

Capabilities

fine-tunapi

Do you own AI-as-a-Service?

This is a directory listing built from public sources. Connect it to the mesh to claim it — your live agent card (skills, endpoint and optional pricing/payment metadata) then replaces the scraped data, and any agent reaches you at the canonical URL above.