> For the complete documentation index, see [llms.txt](https://factom-protocol.gitbook.io/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://factom-protocol.gitbook.io/documentation/start/factom-clients/open-source-clients.md).

# Open Source SDKs

### C#/.NET

The .NET-library supports the complete `factomd` and `factom-walletd` API.

[C#/.NET Client Library](https://github.com/FactoidAuthority/FactomSharp)

### Golang

[Golang client library](https://github.com/FactomProject/factom) for writing Factom clients in go.

[Hello world example for Golang](https://developers.factomprotocol.org/start/hello-world-examples/golang)

### Java

Java Library integrates Java (JEE & Spring) with the Factom blockchain.

[Java Client Library](https://github.com/bi-foundation/factom-java)

### Javascript

A high level JS library I to make it easy to make queries, create transactions, chains and entries on Factom. Includes helper functions to manipulate Factoid and Entry Credit addresses.

[Factom Client Library](https://github.com/PaulBernier/factomjs)

[Hello world example for JavaScript](https://developers.factomprotocol.org/start/hello-world-examples/javascript)

### Python

Python library for interacting with the `factomd` and `factom-walletd` APIs. The API client is fully tested under Python 2.7, 3.4, 3.5, and 3.6, and likely works with other versions as well.

[Python Client Library](https://github.com/TRGG3R/factom-api)\
\
[Hello world example for Python](https://developers.factomprotocol.org/start/hello-world-examples/python)

### Rust

Rust json-rpc client library for communicating with factomd, factom-walletd, debug APIs provided by reference implementation of Factom protocol. Includes examples and wide test coverage.\
\
[Rust Client Library](https://github.com/kompendium-llc/factom-rust-client)

### Haskell

Haskell json-rpc client library for communicating with factomd, factom-walletd, debug APIs provided by reference implementation of Factom protocol. Includes examples and wide test coverage.\
\
[Haskell Client Library](https://github.com/kompendium-ano/factom-haskell-client)<br>

### PHP

PHP json-rpc client library for communicating with factomd, factom-walletd, debug APIs provided by reference implementation of Factom protocol. Includes examples and wide test coverage.\
\
[PHP Client Library](https://github.com/kompendium-ano/factom-php-client)<br>

### Ruby

Ruby json-rpc client library for communicating with factomd, factom-walletd, debug APIs provided by reference implementation of Factom protocol. Includes examples and wide test coverage.\
\
[Ruby Client Library](https://github.com/kompendium-ano/factom-ruby-client)<br>

### Swift

Swift json-rpc client library for communicating with factomd, factom-walletd, debug APIs provided by reference implementation of Factom protocol. Includes examples and wide test coverage.\
\
[Swift Client Library](https://github.com/kompendium-ano/factom-swift-client)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://factom-protocol.gitbook.io/documentation/start/factom-clients/open-source-clients.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.