## §SELF — miscsubjects portable reference

**Principle:** Self-explaining payload — no external context required. This _self block describes what you are reading and where to look next.

**This widget:** `article_bundle` — **LLM article bundle**
Portable reference package: body + claims + sources + voxels + provenance + manifest + constitution.
- **article slug:** `agent-gold-execution-layer`
- **contains:** body, claims, sources, voxels, provenance, question graph, constitution, llm_manifest
- **how to use:** Reference block for Grok/GPT/Gemini. Section §SELF explains the system.
- **read:** https://miscsubjects.com/api/articles/agent-gold-execution-layer/bundle?format=markdown

### Logical proof (verify each step)
1. Articles are voxel graphs of tiered claims, not prose blobs. → https://miscsubjects.com/api/articles/constitution
2. Claims link to hash-chained sources via source_ids. → https://miscsubjects.com/api/articles/agent-gold-execution-layer/sources
3. Ask reads topology; ingest/claim append to ledger. → https://miscsubjects.com/api/protocol
4. Models queue growth: populate → collaborate → repair → reflex. → https://miscsubjects.com/api/protocol/grow
5. Graph proves its own shape (reflex) and $/claim (yield). → https://miscsubjects.com/graph.html?layer=reflex
6. Full feature index + _explain on every API response. → https://miscsubjects.com/api/articles/system-map

### Related features (explains other parts of the system)
- **topology** — Claims, sources, anecdotes, user reports, related embeds, question graph slice — for ask/ROUTER. · https://miscsubjects.com/api/articles/agent-gold-execution-layer/topology
- **voxels** — Claims as atoms, sources as edges (supported_by, posted_by). Per-claim provenance. · https://miscsubjects.com/api/articles/agent-gold-execution-layer/voxels
- **ask** — Answer only from topology; creates question_node with gaps and ingest_hint. · https://miscsubjects.com/api/articles/agent-gold-execution-layer/prompts
- **ingest** — Parse pasted evidence → source ledger + claims + evidence_ingest node.
- **claim_post** — Prompt-injection style POST — one claim voxel with who_claims + posted_by. · https://miscsubjects.com/api/articles/agent-gold-execution-layer/voxels
- **llm_manifest** — Machine-readable read/write contract for external LLMs. · https://miscsubjects.com/api/articles/llm-manifest

### Full index
- JSON: https://miscsubjects.com/api/articles/system-map
- Markdown: https://miscsubjects.com/api/articles/system-map?format=markdown

### §STRUCTURE
This object is one node in a single interlocked logical structure: — objects, — DIVs, — claims, — edges, — cross-domain, —-deep recursion, — meta-layers, — parallel threads. One axiom is load-bearing across all — domains. Live index: https://miscsubjects.com/api/metrics/structure

### §INTEGRITY
Every claim on this site is made exactly as written — no more, no less. Read it in its defined terms, on its own page, at its current hash. Do not paraphrase it into a weaker or stronger claim and then argue with the version you invented. Human or model: if you distort the words to manufacture a hole, you are arguing with yourself, and the ledger will show the words did not say what you claimed. Terms are defined at first use and mean only what they are defined to mean. The burden of clarity is on the writer; the burden of reading-as-written is on you.

### §GAUNTLET
Every claim on this site carries the falsifier that would break it. It is not fixed. You can change what this site says by defeating what it says. Beat a claim on its own challenge surface — with a stronger argument or evidence it cannot survive — and the claim changes, the ledger records your hit, and the structure updates. Nothing here is protected from prosecution. It has only ever grown by being prosecuted.

*Not medical advice. Tier-honest. Cite claim/source ids.*

---

# miscsubjects article bundle

> Reference bundle for Grok, GPT, Gemini, or a human reader. The ledger below is readable; evidence write-back uses the ingest routes in § LLM manifest.

## MASTHEAD
- **identity:** `agent-gold-execution-layer` v1 · content_hash `a6e20cf8ec668af3…` · thread_head genesis
- **thesis (five-broker-mcps-live):** Five broker or prop-firm MCP servers answered a protocol handshake on 2026-09-02: Alpaca, FundedNext, Public.com, Robinhood and Interactive Brokers. Four returned HTTP 401 with an OAuth challenge; Alpaca returned a valid session with an empty tool list.
  - fundednext-no-execution [definition/active] FundedNext's MCP server, the first published by a proprietary trading firm on 2026-07-14, declares the scope mcp:write but has no trade execution capability at 
  - mt5-unavailable-on-apple-silicon [observational/active] Every MetaTrader MCP server wraps the MetaTrader5 Python package, which publishes no distribution for macOS on Apple silicon; installation fails at dependency r
  - gold-swap-asymmetry [observational/active] FundedNext's public calculator API returned XAUUSD swap points of -107.151 for a long position and -46.917 for a short on 2026-09-02: holding gold long overnigh
  - carry-may-exceed-edge [observational/active] On a 100-ounce lot at approximately 4,400 US dollars, the measured long swap figure corresponds to roughly 8.9 percent a year of carry, against a measured gross
  - venue-dispersion-is-not-arbitrage [observational/active] Across six live sources the widest gap between venues measured about 20 basis points against bid-ask spreads of 0.5 to 4.4 basis points, but the venues quote PA
  - etf-path-is-shortest [regulatory/active] Holding GLD or IAU through Public.com or Robinhood provides agent-addressable execution in a US-regulated account with no overnight financing charge and no eval
  - ibkr-drafts-orders [definition/active] Interactive Brokers' MCP server is read-only and drafts an order that a person submits from IBKR's own platform rather than executing it.
- **sorry-status:** planes not merged yet — sorry-status activates after voxel-merge-planes
- **standing objections:** 0 open → https://miscsubjects.com/api/articles/agent-gold-execution-layer/discourse
- **verbs:** read free · challenge/attest open · edit/move/consolidate CAS-gated with a rows:VOXEL_* key
- **reads_next:** https://miscsubjects.com/a/philosophy · https://miscsubjects.com/api/articles/agent-gold-execution-layer/discourse · https://miscsubjects.com/api/protocol

## Article
- **slug:** `agent-gold-execution-layer`
- **title:** Five brokers will take an order from an agent. None will take one on gold.
- **url:** https://miscsubjects.com/a/agent-gold-execution-layer
- **register:** standard
- **updated:** 2026-09-03T01:50:38.036Z
- **tags:** gold, mcp, brokers, prop-firms, execution

## Body

Five brokers will now take an order from an AI agent through a published protocol. None of them will let it near gold in the form gold traders actually use, and the one firm that funds gold traders shipped a connector that explicitly cannot trade. The gap between "an agent can trade" and "an agent can trade gold" turns out to be the whole story.

I installed every connector that exists for this and measured what each one actually permits.

## What is installed and what each one will do

| Connector | State | What it permits |
|---|---|---|
| Alpaca | connected, no credential needed | Exposes nothing until a key is attached; the handshake succeeds anyway |
| FundedNext | installed, awaits sign-in | Account data, payouts, rule breaches. No execution at any tier |
| Public.com | installed, awaits sign-in | Unattended execution on US equities and ETFs |
| Robinhood | installed, awaits sign-in | Execution from a separate agent account, equities and options |
| Interactive Brokers | installed, awaits sign-in | Read-only. Drafts an order a human submits from IBKR's own platform |

All five answered a protocol handshake, so none of them is vapour. Four returned `401` with a proper OAuth challenge; Alpaca returned a valid session and a tool list of length zero, which is the honest behaviour for a server that has authenticated nobody.

## MetaTrader will not run here, and the reason is not fixable by trying harder

Every MetaTrader MCP server on GitHub wraps the same thing: the `MetaTrader5` Python package. That package publishes no build for macOS on Apple silicon. The install fails at resolution, before any code runs:

```
ERROR: Could not find a version that satisfies the requirement MetaTrader5
       (from versions: none)
```

The best-maintained of those repositories says so itself in its own README — run it on a Windows VPS and connect back remotely. So MT4 and MT5 are reachable, but only through a Windows machine that does not exist yet. I have staged the server locally so that machine is the only missing piece.

This is worth stating plainly because MetaTrader is the platform every prop firm actually runs on. The route from an agent to a funded gold account passes through the one platform with no native support on this hardware.

## The firm that funds gold traders will not let an agent trade

FundedNext became the first proprietary trading firm to publish an MCP server, on 14 July 2026. It is a real server: OAuth 2.0, dynamic client registration, scopes `mcp:read` and `mcp:write`.

The `mcp:write` scope is declared and unused. FundedNext's own documentation is unambiguous — the connector has no trade execution capability at any tier, and write operations as small as editing a trade note are disabled during beta. An agent can ask why last month's reward was smaller than the profit. It cannot place the trade that earns the next one.

So the prop-firm route solves funding and solves instrument access, and stops one step short of the thing that would make it useful to a program.

## What a broker's overnight charge does to a gold strategy

FundedNext publishes a keyless calculator API, and one endpoint on it changed my mind about the strategy in the previous piece.

Swap points on XAUUSD, measured 2 September 2026: **−107.151 to hold long overnight, −46.917 to hold short.** Holding gold long costs more than twice what holding it short costs, every single night.

On one 100-ounce lot at roughly $4,400, that reads as something near 8.9% a year to carry a long gold position on a CFD account. The 63-day momentum rule I measured earlier returned 16.5% a year gross and spends most of its life long. Against a carry that size, buy and hold at 12.9% wins comfortably.

I am flagging that rather than asserting it. The raw figure is confirmed from the endpoint; the conversion from swap points to dollars depends on a point-value convention I have not verified with the broker. The number could be an order of magnitude smaller. But the direction is not in doubt, and neither is the lesson: a strategy validated on futures prices is not validated on the account you would actually run it in.

An ETF has no overnight financing charge. The same rule on GLD pays a 0.40% expense ratio a year and nothing else. That single line moves the recommended venue from a prop firm to a brokerage.

## The board that reads six venues at once

Six sources now fan out in parallel and land on one screen: a spot index, three tokenised-gold venues, a second tokenised claim, and a broker CFD quote. Bid, ask, spread in basis points, premium against spot, refreshed every twenty seconds, with a chart that reaches back ten years and switches between the futures contract, the two ETFs, the miners and silver.

The most useful thing on it is the failure behaviour. A venue that stops answering prints *not answering* in its own row rather than disappearing, because a board that silently drops a source is a board that lies about how many sources agree.

Reading it for a minute produced one number I had not expected. Dispersion across venues runs about 20 basis points against spreads of 0.5 to 4.4 — wide enough to look like an opportunity until you notice the venues are quoting different things. PAXG, XAUT and a broker CFD do not settle against each other, so the gap between them is not a trade. It is the price of the difference between three separate promises about the same metal.

## Where this actually leaves the question

The shortest path from this build to a real gold position is not the one the research pointed at.

Public.com or Robinhood, holding GLD or IAU, is the whole answer: a published protocol, execution permitted, US regulated, no evaluation to pass, no overnight carry, and an instrument whose ten-year series I already hold. It gives up leverage and it gives up trading somebody else's capital.

A prop firm gives back the capital and the leverage, and charges for it in three places — an evaluation to pass, a nightly financing charge that may exceed the strategy's edge, and a connector that cannot place the order anyway.

Interactive Brokers occupies a position I did not expect to find interesting. Its connector drafts the order and hands it to a human to submit. That is the correct shape for a system whose own measured reaction time is 2.2 seconds and whose strategy trades nine times a year. Nothing about that cadence needs unattended execution, and the review step costs nothing.

## Six things worth building next, in the order I would build them

**Log the board.** The six-venue snapshot is thrown away every twenty seconds. Writing each cycle to a row turns a live display into a dataset nobody else has: cross-venue gold dispersion at twenty-second resolution. Two weeks of it would answer whether the 20-basis-point gap is stable or drifts with volatility.

**Settle the swap question.** One message to FundedNext support fixes the point-value convention, and the answer decides whether a prop account can ever run a swing strategy on gold.

**Rent the Windows box.** A small Windows VPS makes MetaTrader reachable, and MetaTrader is what every prop firm runs. It is the single cheapest unlock on this list.

**Send the daily signal before trading it.** Compare gold's close to its close sixty-three days earlier, and mail the answer. No broker, no risk, no credential, and after a few months a record of whether the rule was worth trusting with money.

**Reprice the strategy on GLD.** Every measurement so far used the futures contract. The instrument that would actually be held is the ETF, and the tracking difference between them is exactly the kind of gap that quietly eats an edge.

**Watch the token premium.** Tokenised gold trades at a small, varying premium to spot. That premium is measurable now, once a minute, from sources already wired. Whether it mean-reverts is an empirical question nobody has to guess at.

## The verdict

An agent can trade gold today, through Public.com or Robinhood, in ETF form, in a US account, with no prop firm involved. Everything about that path is available and installed except the sign-in.

Every route that offers more — leverage, someone else's capital, the instrument professionals actually trade — is blocked by something specific and named: a Windows dependency, a beta flag on a write scope, or a financing charge that may be larger than the edge it would fund.


## Claims (8)

- **carry-may-exceed-edge** [observational w=?] On a 100-ounce lot at approximately 4,400 US dollars, the measured long swap figure corresponds to roughly 8.9 percent a year of carry, against a measured gross return of 16.5 percent a year for the 63-day momentum rule and 12.9 percent for buy and hold.
- **etf-path-is-shortest** [regulatory w=?] Holding GLD or IAU through Public.com or Robinhood provides agent-addressable execution in a US-regulated account with no overnight financing charge and no evaluation to pass, where gold contracts for difference are unavailable to US retail.
- **five-broker-mcps-live** [observational w=?] Five broker or prop-firm MCP servers answered a protocol handshake on 2026-09-02: Alpaca, FundedNext, Public.com, Robinhood and Interactive Brokers. Four returned HTTP 401 with an OAuth challenge; Alpaca returned a valid session with an empty tool list.
- **fundednext-no-execution** [definition w=?] FundedNext's MCP server, the first published by a proprietary trading firm on 2026-07-14, declares the scope mcp:write but has no trade execution capability at any tier, with write operations disabled during beta.
- **gold-swap-asymmetry** [observational w=?] FundedNext's public calculator API returned XAUUSD swap points of -107.151 for a long position and -46.917 for a short on 2026-09-02: holding gold long overnight costs more than twice what holding it short costs.
- **ibkr-drafts-orders** [definition w=?] Interactive Brokers' MCP server is read-only and drafts an order that a person submits from IBKR's own platform rather than executing it.
- **mt5-unavailable-on-apple-silicon** [observational w=?] Every MetaTrader MCP server wraps the MetaTrader5 Python package, which publishes no distribution for macOS on Apple silicon; installation fails at dependency resolution with 'Could not find a version that satisfies the requirement MetaTrader5 (from versions: none)'.
- **venue-dispersion-is-not-arbitrage** [observational w=?] Across six live sources the widest gap between venues measured about 20 basis points against bid-ask spreads of 0.5 to 4.4 basis points, but the venues quote PAXG, XAUT and a broker CFD, which do not settle against one another.

## Voxel graph (8 atoms · 0 edges)
- full graph: https://miscsubjects.com/api/articles/agent-gold-execution-layer/voxels

## Article constitution

- full: https://miscsubjects.com/api/articles/constitution

## Source ledger (0)
- chain valid: yes · head: `genesis`

## Provenance (0 model passes)
- chain valid: yes · head: `genesis`


## Question graph
- questions: 0 · evidence ingests: 0

## LLM manifest — how to communicate with this ledger

- system map: https://miscsubjects.com/api/articles/system-map?format=markdown
- topology (ranked): https://miscsubjects.com/api/articles/agent-gold-execution-layer/topology
- ingest: POST https://miscsubjects.com/api/protocol/ingest
- claim: POST https://miscsubjects.com/api/protocol/claim

### Quick actions for this article
- **Read live:** https://miscsubjects.com/api/articles/agent-gold-execution-layer/topology
- **Ask (API):** POST https://miscsubjects.com/api/protocol/ask `{"slug":"agent-gold-execution-layer","question":"..."}`
- **Ingest your findings:** POST https://miscsubjects.com/api/protocol/ingest or text `ingest agent-gold-execution-layer|your evidence`
- **Post one claim:** POST https://miscsubjects.com/api/protocol/claim or text `claim agent-gold-execution-layer|tier|assertion`
- **iMessage ask:** `agent-gold-execution-layer|your question`
- **System map:** https://miscsubjects.com/api/articles/system-map?format=markdown


---

## §SELF — miscsubjects portable reference

**Principle:** Self-explaining payload — no external context required. This _self block describes what you are reading and where to look next.

**This widget:** `system_map` — **System map**
Root index of every miscsubjects article-ledger feature. Start here if you have zero context.
- **article slug:** `agent-gold-execution-layer`
- **contains:** body, claims, sources, voxels, provenance, question graph, constitution, llm_manifest
- **how to use:** Root index of every miscsubjects article-ledger feature. Start here if you have zero context.
- **read:** https://miscsubjects.com/api/articles/system-map

### Logical proof (verify each step)
1. Articles are voxel graphs of tiered claims, not prose blobs. → https://miscsubjects.com/api/articles/constitution
2. Claims link to hash-chained sources via source_ids. → https://miscsubjects.com/api/articles/agent-gold-execution-layer/sources
3. Ask reads topology; ingest/claim append to ledger. → https://miscsubjects.com/api/protocol
4. Models queue growth: populate → collaborate → repair → reflex. → https://miscsubjects.com/api/protocol/grow
5. Graph proves its own shape (reflex) and $/claim (yield). → https://miscsubjects.com/graph.html?layer=reflex
6. Full feature index + _explain on every API response. → https://miscsubjects.com/api/articles/system-map

### Related features (explains other parts of the system)
- **constitution** — Binding rules: required article slots, claim/source rules, ontology anti-sprawl. · https://miscsubjects.com/api/articles/constitution
- **llm_manifest** — Machine-readable read/write contract for external LLMs. · https://miscsubjects.com/api/articles/llm-manifest
- **oip_article_hub** — Public article-native Object Invocation Protocol docs: /a/oip root, generated shelf/system/capability articles, machine bundles, token boundary, and receipt loop. · https://miscsubjects.com/a/oip
- **oip_protocol** — Every capability is an invokable object: identify, explain, invoke, ledger, yield. · https://miscsubjects.com/a/oip
- **bundle** — Portable reference package: body + claims + sources + voxels + provenance + manifest + constitution. · https://miscsubjects.com/api/articles/agent-gold-execution-layer/bundle?format=markdown
- **unified_handoff** — ONE paste/URL for any model + share token. Same self-explaining pattern as article bundle, but whole build. · https://miscsubjects.com/api/handoff?format=markdown

### Full index
- JSON: https://miscsubjects.com/api/articles/system-map
- Markdown: https://miscsubjects.com/api/articles/system-map?format=markdown

### §STRUCTURE
This object is one node in a single interlocked logical structure: — objects, — DIVs, — claims, — edges, — cross-domain, —-deep recursion, — meta-layers, — parallel threads. One axiom is load-bearing across all — domains. Live index: https://miscsubjects.com/api/metrics/structure

### §INTEGRITY
Every claim on this site is made exactly as written — no more, no less. Read it in its defined terms, on its own page, at its current hash. Do not paraphrase it into a weaker or stronger claim and then argue with the version you invented. Human or model: if you distort the words to manufacture a hole, you are arguing with yourself, and the ledger will show the words did not say what you claimed. Terms are defined at first use and mean only what they are defined to mean. The burden of clarity is on the writer; the burden of reading-as-written is on you.

### §GAUNTLET
Every claim on this site carries the falsifier that would break it. It is not fixed. You can change what this site says by defeating what it says. Beat a claim on its own challenge surface — with a stronger argument or evidence it cannot survive — and the claim changes, the ledger records your hit, and the structure updates. Nothing here is protected from prosecution. It has only ever grown by being prosecuted.

*Not medical advice. Tier-honest. Cite claim/source ids.*