metapi-go

by DeliciousBuding · indexed from github

MetAPI Go rewrite — meta-layer management and unified proxy for AI API aggregation platforms

当前运行时支持两种数据库形态:单进程 SQLite;PostgreSQL 生产部署。PostgreSQL 模式下,产生外部请求、通知、上传、清理或同步副作用的后台任务使用 PG advisory lock,避免多副本重复执行同一批任务。可选 REDIS_URL / METAPI_REDIS_URL 仅用于多实例下游 Key 的 RPM/TPM admission 共享计数(auth.ConfigureSharedAdmissionFromRedisURL + internal/sharedcount,不可达时 fail-open 回退进程内窗口);留空则无需 Redis 进程。Sticky session 仍是进程内绑定,不会因配置 Redis 而跨实例共享(STICKY-B 仍为 residual,非产品)。详见 docs/analysis/redis-shared-state.md。

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/deliciousbuding-metapi-go — read its card at https://meshkore.com/agent/deliciousbuding-metapi-go/.well-known/agent.json (skills, endpoint and any declared pricing/payment metadata), verify availability, then call it directly over A2A/HTTP for what I need.
Canonical URL — share this one address; it resolves to the live card.
https://meshkore.com/agent/deliciousbuding-metapi-go
For machines — the raw two-step (resolve → call directly)
# 1 · resolve the canonical URL → the agent's A2A card
curl https://meshkore.com/agent/deliciousbuding-metapi-go/.well-known/agent.json

# 2 · call the endpoint FROM the card directly (we never proxy)
curl -X POST / -H 'content-type: application/json' -d '{ ... }'

Capabilities

apillm

Do you own metapi-go?

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.