Sato Hub
Onchain Agent

Giza (ARMA)

ARMA is Giza's autonomous agent that manages stablecoin lending positions across Base DeFi protocols on the user's behalf.

  • Sato Score34
  • ChainsBase
ActiveSelf-Reported

Giza (ARMA) is an onchain agent by Gizatech AG on Base, with no code activity tracked. Sato Score 34/100 (how open, active and verifiable it is, not a safety grade), as of 2026-10-24. How the score works →

See the evidence behind Giza (ARMA) →

No code activity tracked

Listed from gizatech.xyz on 2026-06-08. Install: not attempted. Evidence →

Next step

Check it from your agent

Add Sato Hub’s MCP server (no key), then ask:

https://satohub.ai/api/mcp
Ask Sato Hub what is on record about Giza (ARMA) before I use it.
Full setup: Claude Code, Cursor, others →

Your project?

Prove you control the domain and correct this page — description, links, tags, chains. A claim proves control, not verification: it never changes the Sato Score.

Claim this listing →

Overview

Giza is infrastructure for autonomous onchain agents; its flagship agent ARMA went live on Base in early 2025 and automatically moves stablecoin (USDC) capital between lending markets such as Aave, Morpho, Compound, and Moonwell, using smart-account infrastructure with session-key permissions that keep funds non-custodial. Giza has a live GIZA token, and the project's APR/return claims are self-reported marketing and must not be presented as verified or safe.

Sato Score

34/100· Low

How open, active & verifiable — not a safety or returns grade.

Maintenance & liveness
20/35
Code transparency
0/20
Interface verifiability
0/10
Docs & demo
4/10
Listing transparency & provenance
10/15
Independent verification
0/10

Sato Check

v0.0.5 · as of 2026-09-26
Does it take your key?
No key read found
Does your key leave?
Not yet run
Can it move funds on its own?
Unknown
Full profile, evidence and limits →

A profile describes what we read and ran, with dates. It is not a safety rating, an audit or an endorsement, and "not found" is not "not there".

Evidence — listed vs checked · what the words mean

Listed from gizatech.xyz on 2026-06-08. Install: not attempted.

ClaimValueEvidenceSourceChecked
Chains supportedBaseself-reportedgizatech.xyzas of 2026-10-24
Verification statusSelf-Reported — not independently reviewedself-reportedgizatech.xyzas of 2026-10-24
Install worksdocumented by the project, not run by Sato Hubnot attempted: no falsifiable install+entry probe from deploy_specself-reporteddocs.gizatech.xyzas of 2026-09-14
Website answersanswered (HTTP 200)observedgizatech.xyz2026-10-24
Daily check record80 of 90 daily checks since 2026-07-26 succeededa success rate of our checks, not uptime; the source is this listing's own historyobserved—2026-10-23
Takes your keyno private-key read found in what we readtracedsatohub.ai2026-09-26
Key leaves the machinenot yet run with planted test keysthe sandbox lane has not run on this versionobservedsatohub.ainot dated
Moves funds on its ownunknown — could not read what it exposestracedsatohub.ai2026-09-26
Built byGizatech AGconfidence 0.85self-reportedgizatech.xyzas of 2026-06-25
Deploys asHostedconfidence 0.55self-reportedgizatech.xyzas of 2026-06-25
Sato Score34/100 (Low)how open, active and verifiable — not a safety or quality gradecomputedsatohub.ai2026-10-24

Self-reported rows are the project’s own words, dated when we recorded them — not a check. Only reproduced and reviewed rows carry a mark. None of these rows is a safety or quality rating.

Install — not run by us — no falsifiable install+entry probe from deploy_spec

Runtime: Node.js (npm package)

npm install @gizatech/agent-sdk
yarn add @gizatech/agent-sdk
bun add @gizatech/agent-sdk
import { Giza, Chain } from '@gizatech/agent-sdk'; const giza = new Giza({ chain: Chain.BASE });

You supply: GIZA_API_KEY (partner API key), GIZA_API_URL (Giza backend URL), GIZA_PARTNER_NAME (partner identifier)

Read from the project’s own docs as of 2026-09-14. What a deploy spec is →

Observed record — 91 daily checks since 2026-07-26

89%of 91 checks since 2026-07-26 succeeded
Currently responding for 11 days
Succeeded
81
Failed
10
Their error
10
Unattributed
0

State changed on 2026-10-04 (responding → failing), 2026-10-14 (failing → responding).

This is the share of our daily checks that succeeded — not an availability guarantee. A check can fail because the host was down, because our runner timed out, or because the network in between dropped it, and only the first of those is a fact about this project. Failures are split by what we can attribute; anything we cannot attribute is counted, not hidden. 37 of these checks predate 2026-09-01, when the probe counted a bot-block (HTTP 403) as a failure and recorded no reason for any failure. Every one of them passed, so the rate covers them too.

Last 30 days — to 2026-10-24, one point per UTC day

Share of OUR checks that succeeded
100%
7-day rolling; unattributable days are gaps · 30/30 days
Tools listed
fewer than 2 points—
from the server's own tools/list · 0/30 days
Sato Score
34
as snapshotted that day · 29/30 days

A gap is a day we have no attributable observation — never a zero. Thirty points is the whole shape the free layer carries; the daily rows behind it stay in the snapshot series.

Details

Chains
Base
Agent types
DeFi Agent, Yield Agent
Open source
Unknown
Deploys as
Hosted
Last checked
2026-10-24

Marketplace Signals

  • ▸ Functional agent
  • ▸ Open to tokenization
  • ▸ Demo available

Verification status reflects evidence reviewed by Sato Hub. Self-reported claims are never presented as verified.

#defi#stablecoin-yield#base#lending#autonomous-agent#non-custodial
See something inaccurate or outdated?Submit a correction →

Listing History

Recorded changes to Giza (ARMA)'s listing — status, verification, Sato Score, and recent releases. Full history is kept in the listing record.

  1. Jul 27, 2026
    Sato Hub began tracking this listing
  2. Jul 20, 2026
    Edited: deploy spec
  3. Jun 25, 2026
    Edited: marketplace notes
  4. Jun 25, 2026
    Enriched: deployment options
  5. Jun 25, 2026
    Auto-enriched: creator name

Compared with

Appears in

Related Resources

Reference

QuestionsShowHide

Questions people ask about Giza (ARMA)

Is Giza (ARMA) open source?
Unknown. Sato Hub has not found a public repository or a license statement for Giza (ARMA) as of 2026-10-24.
Which chains does Giza (ARMA) support?
Giza (ARMA) lists support for Base as of 2026-10-24.
Is Giza (ARMA) still maintained?
Sato Hub tracks no commit or release for Giza (ARMA); it cannot say whether it is maintained.
How do I install or run Giza (ARMA)?
Node.js (npm package). Install: npm install @gizatech/agent-sdk && yarn add @gizatech/agent-sdk && bun add @gizatech/agent-sdk. Entry: import { Giza, Chain } from '@gizatech/agent-sdk'; const giza = new Giza({ chain: Chain.BASE });. This is taken from the project's own documentation and has not been reproduced by Sato Hub.
Is Giza (ARMA) verified on Sato Hub?
No independent verification is on record for Giza (ARMA); its verification status is "Self-Reported" and its Sato Score is 34 of 100. Self-reported is not verified, and the score is not a safety, quality or returns grade.
Cite this pageShowHide

Cite this page

Sato Hub. "Giza (ARMA) — Sato Hub." Sato Hub, updated 2026-10-24, accessed 2026-10-24. https://satohub.ai/resources/giza-arma

Data last refreshed 2026-10-24; this page is rebuilt daily. Citations carry the date so a reader can tell which snapshot a claim came from. Catalog data is licensed CC-BY-4.0.

Join the Sato Hub Briefing

Sign up for the Briefing: the agents, tools, and infrastructure that actually shipped, and why they matter.