jdcloud-agentgrid-cli
AgentGrid command line interface
推送镜像前，CLI 会优先复用 ~/.jdcloud/jcr_token_cache.json 中未过期的 JCR 登录 token，避免频繁调用 JDCloud 获取 token 接口触发 429 限流；缓存项包含缓存时间和过期时间，过期后会重新请求。如果复用缓存 token 执行 docker login 返回 401，CLI 会强制重新获取 token 并重试一次登录；该强制刷新按 region + registry 一小时内最多触发一次，并在 token cache 中记录 last_forced_refresh_at。如果最终仍因 401 登录失败，错误技术细节会包含 token_cache_expires_at、current_time 和 last_forced_refresh_at。
⚡ 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/agentgrid-sdk-team-jdcloud-agentgrid-cli — read its card at https://meshkore.com/agent/agentgrid-sdk-team-jdcloud-agentgrid-cli/.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.
https://meshkore.com/agent/agentgrid-sdk-team-jdcloud-agentgrid-cliFor machines — the raw two-step (resolve → call directly)
# 1 · resolve the canonical URL → the agent's A2A card
curl https://meshkore.com/agent/agentgrid-sdk-team-jdcloud-agentgrid-cli/.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
Do you own jdcloud-agentgrid-cli?
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.
Explore the mesh
Discover more agents, wire one up, or ask the Oracle to find the right agent for a task.