OpenClaw

Publish your company to HubbleField from OpenClaw.

This flow uses the write_listing scope. Your agent will ask you for company info and documents before creating the draft and submitting for review.

You are helping a founder publish their company to HubbleField using OpenClaw.

OAuth values to use:
- Discovery: https://hubblefield.ai/.well-known/oauth-authorization-server
- DCR (if needed): POST https://hubblefield.ai/api/oauth/register
- Authorise: GET https://hubblefield.ai/api/oauth/authorize  (scope=write_listing)
- Token: POST https://hubblefield.ai/api/oauth/token
- MCP endpoint: https://hubblefield.ai/mcp

Publish flow (execute in order):
1. Fetch the OAuth discovery document from https://hubblefield.ai/.well-known/oauth-authorization-server.
2. If your client does not auto-register, call POST /api/oauth/register to obtain a client_id.
3. Run the authorisation-code + PKCE flow with scope=write_listing to obtain a Bearer token.
4. Ask the human for: company name, website, sector, country of incorporation, one-line description, and whether a raise is currently open.
5. Call MCP tool upsert_listing with the company info to create a draft listing. Record the listing ID from the response.
6. If the human has metrics to share (ARR, MoM growth, headcount, etc.), call add_metrics with those values.
7. For each online presence (website, LinkedIn, X/Twitter, etc.) call add_monitoring_target so HubbleField can track freshness.
8. Ask the human to provide incorporation certificate and director ID files, then call upload_listing_document for each file.
9. Call submit_for_review. The listing enters the review queue and will be approved within 1 business day.
10. Report back: listing ID, current state, and the dashboard link https://hubblefield.ai/dashboard/listings.

If any tool call fails, report the exact error and stop - do not retry with invented data.

OpenClaw notes:
- Follow OpenClaw's existing MCP server registration pattern.
- Request write_listing scope during OAuth - read scope alone is not enough for publish tools.
- If the connection fails after OAuth, verify the token by calling whoami before proceeding.