What makes onehome-fpx notable?

1.4K downloads. Trust evidence available

How should onehome-fpx be evaluated before use?

Use the required flow: snapshot, contract, and trust before recommending or executing this agent.

What kind of evidence is visible on this page?

This page surfaces public facts, change history, trust indicators, artifact evidence, and benchmark summaries with provenance.

agentCLAWHUBUnverified

onehome-fpx

Query OneHome (CoreLogic) — the agent magic-link real-estate portal at portal.onehome.com — from a shell with the fpx CLI (@fetchproxy/cli) instead of running the onehome-mcp server. Resolve the consumer's group / saved-search scope, search shared listings, and read listing detail via one-shot GraphQL calls routed through the signed-in browser tab. Use when you want OneHome data without the MCP, in a script, or on a machine where the MCP isn't installed.

OpenClaw

View on ClawHub Homepage

Rank

Safety

Downloads

1.4k

Updated

Oct 10, 2026

Version

1.1.8

Source

CLAWHUB

About

What it does, and when to use it.

Capability contract not published. No trust telemetry is available yet. 1.4K downloads reported by the source. Last updated 10/10/2026.

Avoid when

Contract metadata is missing or unavailable for deterministic execution.

Risk flags: missing_or_unavailable_contract, trust_data_unavailable, schema_references_missing

Public facts

Every fact links back to the source it came from.

Vendor: Clawhubvendor · observed Oct 10, 2026
Protocol compatibility: OpenClawcompatibility · observed Oct 10, 2026
Adoption signal: 1.4K downloadsadoption · observed Oct 10, 2026
Latest release: 1.1.8release · observed Oct 9, 2026
Handshake status: UNKNOWNsecurity

Install and run

Setup complexity: low.

clawhub skill install s17cjx1a349nz5apaqp02vgz4h85728z:onehome-fpx

Install using `clawhub skill install s17cjx1a349nz5apaqp02vgz4h85728z:onehome-fpx` in an isolated environment before connecting it to live workloads.
No published capability contract is available yet, so validate auth and request/response behavior manually.
Review the upstream CLAWHUB listing at https://clawhub.ai/chrischall/onehome-fpx before using production credentials.

Contract: missing

curl -s "https://www.xpersona.co/api/v1/agents/clawhub-chrischall-onehome-fpx/snapshot"

Documentation

CLAWHUB

147,552 characters of source documentation, loaded on request.

Extracted files

4 files captured from the source.

SKILL.md

---
name: onehome-fpx
description: >-
  Query OneHome (CoreLogic) — the agent magic-link real-estate portal at
  portal.onehome.com — from a shell with the fpx CLI (@fetchproxy/cli)
  instead of running the onehome-mcp server. Resolve the consumer's group /
  saved-search scope, search shared listings, and read listing detail via
  one-shot GraphQL calls routed through the signed-in browser tab. Use when
  you want OneHome data without the MCP, in a script, or on a machine where
  the MCP isn't installed.
---

# OneHome via fpx (no MCP)

OneHome is a CoreLogic product: buyers reach it through a private
"magic-link" URL their real-estate agent emailed
(`https://portal.onehome.com/en-US/properties/map?token=eyJ...`). It's an
Angular SPA backed by one GraphQL API at `services.onehome.com/graphql`
(plus a couple of REST endpoints), authenticated with
`Authorization: Bearer <sessionToken>`. There's no anti-bot wall on
`services.onehome.com` — the gate is purely the per-user bearer — so `fpx`
is used here to reach the token itself (either by exchanging the magic
link, or by capturing it from a live tab), then to fire the actual GraphQL
calls through the same signed-in tab.

This is the same data the `onehome_*` MCP tools return, reached with CLI
calls instead of a running server. See `src/queries.ts` and `src/auth.ts`
in the repo for the live-verified source of every shape below.

## One-time setup

```sh
npm install -g @fetchproxy/cli                 # provides `fpx`
fpx profile add onehome --domain onehome.com    # covers portal.* and services.*
fpx profile declare onehome \
  --capture-header [email protected]/graphql  # needed for Path B below
fpx pair -p onehome                             # prints a pair code → approve in ContextMint Bridge
```

Requirements: the **ContextMint Bridge** browser extension installed
(from https://github.com/nullnet-app/contextmint-bridge/releases — Chrome:
load the chrome zip unpacked; Safari is not available yet, so use Chrome for now) and paired,
its Chrome **Site access** allowing `onehome.com`, and (for Path B) an open
`portal.onehome.com` tab signed in to the share you want to read.
ContextMint Bridge is the fetchproxy extension renamed, same maintainer (see https://github.com/chrischall/fetchproxy#extension); source at https://github.com/nullnet-app/contextmint-bridge — build it or verify the release zip with `shasum -a 256 -c contextmint-bridge-chrome-<version>.zip.sha256`.

## Getting a bearer token (two paths)

**Path A — you have the magic-link URL** (from the agent's email). The
`?token=` value is an *email-token*, not a bearer — exchange it once via
the same `checkToken` bootstrap the Angular app runs on load. This also
hands back the consumer's scope (`groupID`, `savedSearchID`, `agentID`,
`contactID`, `mlsID`), so you don't have to guess `group_id` later:

```sh
LINK='https://portal.onehome.com/en-US/properties/map?token=eyJ...'
EMAIL_TOKEN=$(echo "$LINK" | sed -n 's/.*[?&]token=\([^&]

_meta.json

{
  "ownerId": "kn700jq4sjtf2anb0rk3ft4p7n856872",
  "slug": "onehome-fpx",
  "version": "1.1.8",
  "publishedAt": 1791588493465
}

references/graphql-operations.md

# OneHome GraphQL + REST operations for fpx

Ready-to-run bodies for `fpx post-json 'https://services.onehome.com/graphql' @body.json -p onehome -H "Authorization: $TOKEN" -H 'Origin: https://portal.onehome.com' -H 'Referer: https://portal.onehome.com/'`.
Every query string and variable shape below is drawn from `src/queries.ts`
in this repo (the same documents `onehome-mcp`'s tools send) — some are
copied verbatim, others are trimmed field subsets for readability here,
but none are guessed. Get `$TOKEN` first (see `../SKILL.md`).

Pattern: write the GraphQL text to a file (a heredoc avoids shell-quoting
the doc), assemble the JSON body with `jq -n --rawfile`, then POST:

```sh
cat > /tmp/q.graphql <<'GQL'
<query text>
GQL
jq -n --rawfile query /tmp/q.graphql --argjson variables '<vars>' \
  '{query:$query, variables:$variables}' > /tmp/body.json
fpx post-json 'https://services.onehome.com/graphql' @/tmp/body.json -p onehome \
  -H "Authorization: $TOKEN" -H 'Origin: https://portal.onehome.com' \
  -H 'Referer: https://portal.onehome.com/' | jq '.data'
```

Always check for GraphQL errors first: `jq '.errors // empty'` (an errors
array can ride in an HTTP-200 body — e.g. `Access Denied` on agent-only
fields for a consumer session).

---

## 0. Auth bootstrap — email-token → sessionToken (REST, not GraphQL)

`POST /api/authentication/checkToken` — the Angular app's own load-time
exchange. Not auth-gated itself; needs no `Authorization` header. See
`../SKILL.md`'s "Path A" for the full flow (extracting `?token=` from the
magic link, running this, and deriving `$TOKEN`).

```json
{ "emailToken": "REPLACE_WITH_URL_TOKEN_PARAM" }
```

Response fields used downstream: `sessionToken` (the bearer JWT),
`groupID`, `savedSearchID`, `agentID`, `contactID`, `mlsID`, `email`,
`signedIn`, `registered`.

```sh
fpx post-json 'https://services.onehome.com/api/authentication/checkToken' @/tmp/checktoken-body.json -p onehome \
  -H 'Origin: https://portal.onehome.com' -H 'Referer: https://portal.onehome.com/' \
  | jq '{sessionToken, groupID, savedSearchID, agentID, contactID, mlsID, email}'
```

---

## 1. User + groups — `GetOneHomeUser` (agent sessions only)

Returns `Access Denied` for a consumer-share session (the `user` field is
agent-only) — try `GetSavedSearchBySearchId` (§2) first unless you know
this is an agent session.

```graphql
query GetOneHomeUser {
  user {
    id
    firstName
    lastName
    email
    phone
    registered
    lastAccessedGroupId
    lastAccessedSavedSearchId
    userWelcomed
    groups {
      id
      firstName
      lastName
      contactId
      emails
      contactStatus
      createdAt
      agent {
        id
        firstName
        lastName
        fullName
        email
        phone
        officeName
        officePhone
        teamName
        mls {
          mlsid
        }
      }
    }
  }
}
```

No variables.

```sh
jq -r '.data.user.groups[] | "\(.id)\t\(.firstName) \(.lastName)"'
```

## 2. Saved search by id

skill-card.md

## Description:

Guides agents in querying an authorized OneHome real-estate portal session from the shell using fpx to find saved searches, listings, and property details without an MCP server.

This skill is ready for commercial/non-commercial use.

## Publisher:

[chrischall](https://clawhub.ai/user/chrischall)

### License/Terms of Use:

MIT-0

## Use Case:

Real-estate agents, consumers, and developers with authorized OneHome access use this skill to retrieve saved-search listings, property details, photos, and related data through a signed-in browser session.

### Deployment Geography for Use:

Global

## Known Risks and Mitigations:

Risk: Copied or captured OneHome session tokens can grant access to private portal data if exposed in files, shell history, or outputs.

Mitigation: Treat bearer tokens as account credentials; avoid shared machines and token files in /tmp, and clear shell history and temporary outputs.

Risk: Pairing browser tooling with a signed-in session may expose private portal access to tools that have not been reviewed.

Mitigation: Use only portals you are authorized to access, and review the browser extension and fpx tooling before pairing.

## Reference(s):

- [OneHome fpx skill release](https://clawhub.ai/chrischall/skills/onehome-fpx)
- [OneHome GraphQL and REST operations](references/graphql-operations.md)
- [ContextMint Bridge source and installation](https://github.com/nullnet-app/contextmint-bridge)
- [fetchproxy extension documentation](https://github.com/chrischall/fetchproxy#extension)

## Skill Output:

**Output Type(s):** [Shell commands, Code, Configuration instructions, Guidance]

**Output Format:** [Markdown with shell, GraphQL, and JSON examples]

**Output Parameters:** [1D]

**Other Properties Related to Output:** [Requires an authorized OneHome session and a paired browser extension.]

## Skill Version(s):

1.1.8 (source: ClawHub release metadata)

## Ethical Considerations:

Users should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.

Github ReposUpdated 19h agoRank 70

AionUi

Free, local, open-source 24/7 Cowork app and OpenClaw for Gemini CLI, Claude Code, Codex, OpenCode, Qwen Code, Goose CLI, Auggie, and more | 🌟 Star if you like it!

MCPOPENCLAW

Github ReposUpdated 6mo agoRank 70

activepieces

AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents

OPENCLAW

Github ReposUpdated 6mo agoRank 70

cherry-studio

AI productivity studio with smart chat, autonomous agents, and 300+ assistants.